e01b4f6 ci: replace platform linux with windows 11

app-shell/schema.d.ts

@@ -1,7 +1,7 @@
 /**
  * Configures your project to generate an app-shell during build time.
  */
-export interface Schema {
+export type Schema = {
     /**
      * The name of the project where the app-shell should be generated.
      */
@@ -11,4 +11,4 @@ export interface Schema {
      * Preview).
      */
     serverRouting?: boolean;
-}
+};

application/schema.d.ts

@@ -4,7 +4,7 @@
  * configuration files. You can customize various aspects of the application, such as
  * routing, styling, and testing.
  */
-export interface Schema {
+export type Schema = {
     /**
      * Generate an application that does not use `zone.js`.
      */
@@ -90,7 +90,7 @@ export interface Schema {
      * component styles are scoped and applied.
      */
     viewEncapsulation?: ViewEncapsulation;
-}
+};
 /**
  * The type of stylesheet files to be created for components in the application.
  */

class/schema.d.ts

@@ -4,7 +4,7 @@
  * with properties and methods. This schematic helps you generate a new class with the basic
  * structure and optional test files.
  */
-export interface Schema {
+export type Schema = {
     /**
      * The name for the new class. This will be used to create the class file (e.g.,
      * `my-class.ts`) and, if enabled, the corresponding test file `my-class.spec.ts`.
@@ -29,4 +29,4 @@ export interface Schema {
      * For example, if you set the type to `helper`, the filename will be `my-class.helper.ts`.
      */
     type?: string;
-}
+};

component/schema.d.ts

@@ -3,7 +3,7 @@
  * applications. Each component consists of a TypeScript class, an HTML template, and an
  * optional CSS stylesheet. Use this schematic to generate a new component in your project.
  */
-export interface Schema {
+export type Schema = {
     /**
      * Configures the change detection strategy for the component.
      */
@@ -103,7 +103,7 @@ export interface Schema {
      * styles are scoped and applied.
      */
     viewEncapsulation?: ViewEncapsulation;
-}
+};
 /**
  * Configures the change detection strategy for the component.
  */

config/schema.d.ts

@@ -3,7 +3,7 @@
  * your project's build process, testing, and browser compatibility. This schematic helps
  * you create or update essential configuration files with ease.
  */
-export interface Schema {
+export type Schema = {
     /**
      * The name of the project where the configuration file should be created or updated.
      */
@@ -12,7 +12,7 @@ export interface Schema {
      * Specifies the type of configuration file to generate.
      */
     type: Type;
-}
+};
 /**
  * Specifies the type of configuration file to generate.
  */

directive/schema.d.ts

@@ -4,7 +4,7 @@
  * custom attributes, and respond to events. This schematic generates the necessary files
  * and boilerplate code for a new directive.
  */
-export interface Schema {
+export type Schema = {
     /**
      * Automatically export the directive from the specified NgModule, making it accessible to
      * other modules in the application.
@@ -59,4 +59,4 @@ export interface Schema {
      * other standalone components or directives.
      */
     standalone?: boolean;
-}
+};

e2e/schema.d.ts

@@ -1,7 +1,7 @@
 /**
  * Generates a new, generic end-to-end test definition in the given project.
  */
-export interface Schema {
+export type Schema = {
     /**
      * The name of the application being tested.
      */
@@ -10,4 +10,4 @@ export interface Schema {
      * The HTML selector for the root component of the test app.
      */
     rootSelector?: string;
-}
+};

enum/schema.d.ts

@@ -3,7 +3,7 @@
  * named constants, making your code more readable and maintainable. This schematic
  * generates a new enum with the specified name and type.
  */
-export interface Schema {
+export type Schema = {
     /**
      * The name for the new enum. This will be used to create the enum file (e.g.,
      * `my-enum.enum.ts`).
@@ -24,4 +24,4 @@ export interface Schema {
      * For example, if you set the type to `status`, the filename will be `my-enum.status.ts`.
      */
     type?: string;
-}
+};

environments/schema.d.ts

@@ -4,9 +4,9 @@
  * development, testing, and production. This schematic helps you create and manage these
  * files, making it easier to customize your application's behavior for each environment.
  */
-export interface Schema {
+export type Schema = {
     /**
      * The name of the project where the environment files should be created or updated.
      */
     project: string;
-}
+};

guard/schema.d.ts

@@ -3,7 +3,7 @@
  * parts of your application by checking certain conditions before a route is activated.
  * This schematic generates a new guard with the specified name, type, and options.
  */
-export interface Schema {
+export type Schema = {
     /**
      * Creates the new guard files at the top level of the current project. If set to false, a
      * new folder with the guard's name will be created to contain the files.
@@ -40,7 +40,7 @@ export interface Schema {
      * Skip the generation of a unit test file `spec.ts` for the new guard.
      */
     skipTests?: boolean;
-}
+};
 export declare enum Implement {
     CanActivate = "CanActivate",
     CanActivateChild = "CanActivateChild",

interceptor/schema.d.ts

@@ -4,7 +4,7 @@
  * perform tasks like adding authentication headers, handling errors, or logging requests.
  * This schematic generates the necessary files and boilerplate code for a new interceptor.
  */
-export interface Schema {
+export type Schema = {
     /**
      * Creates the new interceptor files at the top level of the current project. If set to
      * false, a new folder with the interceptor's name will be created to contain the files.
@@ -35,4 +35,4 @@ export interface Schema {
      * Skip the generation of a unit test file `spec.ts` for the new interceptor.
      */
     skipTests?: boolean;
-}
+};

interface/schema.d.ts

@@ -3,7 +3,7 @@
  * TypeScript, ensuring type safety and code clarity. This schematic generates a new
  * interface with the specified name and type.
  */
-export interface Schema {
+export type Schema = {
     /**
      * The name for the new interface. This will be used to create the interface file (e.g.,
      * `my-interface.interface.ts`).
@@ -30,4 +30,4 @@ export interface Schema {
      * `my-interface.data.ts`.
      */
     type?: string;
-}
+};

library/schema.d.ts

@@ -4,7 +4,7 @@
  * across multiple applications. This schematic simplifies the process of generating a new
  * library with the necessary files and configurations.
  */
-export interface Schema {
+export type Schema = {
     /**
      * The path to the library's public API file, relative to the workspace root. This file
      * defines what parts of the library are accessible to applications that import it.
@@ -47,4 +47,4 @@ export interface Schema {
      * This can simplify the structure of your library and its usage in applications.
      */
     standalone?: boolean;
-}
+};

module/schema.d.ts

@@ -1,7 +1,7 @@
 /**
  * Creates a new, generic NgModule definition in the given project.
  */
-export interface Schema {
+export type Schema = {
     /**
      * The new NgModule imports "CommonModule".
      */
@@ -40,7 +40,7 @@ export interface Schema {
      * The scope for the new routing module.
      */
     routingScope?: RoutingScope;
-}
+};
 /**
  * The scope for the new routing module.
  */

ng-new/schema.d.ts

@@ -4,7 +4,7 @@
  * an optional starter application. You can customize various aspects of the workspace and
  * the initial project, such as routing, styling, and testing.
  */
-export interface Schema {
+export type Schema = {
     /**
      * Configure the initial Git commit for the new repository.
      */
@@ -115,17 +115,17 @@ export interface Schema {
      * encapsulated using Shadow DOM).
      */
     viewEncapsulation?: ViewEncapsulation;
-}
+};
 /**
  * Configure the initial Git commit for the new repository.
  */
 export type CommitUnion = boolean | CommitObject;
-export interface CommitObject {
+export type CommitObject = {
     email: string;
     message?: string;
     name: string;
     [property: string]: any;
-}
+};
 /**
  * The package manager used to install dependencies.
  */

package.json

@@ -1,6 +1,6 @@
 {
   "name": "@schematics/angular",
-  "version": "19.2.0-next.0+sha-197b770",
+  "version": "19.2.0-next.0+sha-e01b4f6",
   "description": "Schematics specific to Angular",
   "homepage": "https://github.com/angular/angular-cli",
   "keywords": [
@@ -22,8 +22,8 @@
   },
   "schematics": "./collection.json",
   "dependencies": {
-    "@angular-devkit/core": "github:angular/angular-devkit-core-builds#197b770",
-    "@angular-devkit/schematics": "github:angular/angular-devkit-schematics-builds#197b770",
+    "@angular-devkit/core": "github:angular/angular-devkit-core-builds#e01b4f6",
+    "@angular-devkit/schematics": "github:angular/angular-devkit-schematics-builds#e01b4f6",
     "jsonc-parser": "3.3.1"
   },
   "repository": {

pipe/schema.d.ts

@@ -4,7 +4,7 @@
  * dates, currency, or filtering arrays. This schematic generates the necessary files and
  * boilerplate code for a new pipe.
  */
-export interface Schema {
+export type Schema = {
     /**
      * Automatically export the pipe from the specified NgModule, making it accessible to other
      * modules in the application.
@@ -49,4 +49,4 @@ export interface Schema {
      * standalone components, directives, or pipes.
      */
     standalone?: boolean;
-}
+};

resolver/schema.d.ts

@@ -4,7 +4,7 @@
  * displayed. This can improve the user experience by preventing delays and loading states.
  * This schematic generates a new resolver with the specified name and options.
  */
-export interface Schema {
+export type Schema = {
     /**
      * Creates the new resolver files at the top level of the current project. If set to false,
      * a new folder with the resolver's name will be created to contain the files.
@@ -34,4 +34,4 @@ export interface Schema {
      * Skip the generation of a unit test file `spec.ts` for the new resolver.
      */
     skipTests?: boolean;
-}
+};

server/schema.d.ts

@@ -3,7 +3,7 @@
  * be rendered on the server, improving initial load performance and SEO. This schematic
  * configures your project for SSR and generates the necessary files.
  */
-export interface Schema {
+export type Schema = {
     /**
      * The name of the project to enable server-side rendering for.
      */
@@ -18,4 +18,4 @@ export interface Schema {
      * dependencies later.
      */
     skipInstall?: boolean;
-}
+};

service-worker/schema.d.ts

@@ -3,7 +3,7 @@
  * offline or on low-quality networks by caching assets and intercepting network requests.
  * This schematic configures your project to use a service worker.
  */
-export interface Schema {
+export type Schema = {
     /**
      * The name of the project to add the service worker to. If not specified, the CLI will
      * determine the project from the current directory.
@@ -14,4 +14,4 @@ export interface Schema {
      * that the service worker should be generated during the standard build process.
      */
     target?: string;
-}
+};

service/schema.d.ts

@@ -3,7 +3,7 @@
  * such as data access, API calls, or utility functions. This schematic simplifies the
  * process of generating a new service with the necessary files and boilerplate code.
  */
-export interface Schema {
+export type Schema = {
     /**
      * Creates files at the top level of the project or the given path. If set to false, a new
      * folder with the service's name will be created to contain the files.
@@ -28,4 +28,4 @@ export interface Schema {
      * Skip the generation of a unit test file `spec.ts` for the service.
      */
     skipTests?: boolean;
-}
+};

ssr/schema.d.ts

@@ -5,7 +5,7 @@
  * generating the necessary files and making the required modifications to your project's
  * structure.
  */
-export interface Schema {
+export type Schema = {
     /**
      * The name of the project you want to enable SSR for.
      */
@@ -20,4 +20,4 @@ export interface Schema {
      * dependencies later.
      */
     skipInstall?: boolean;
-}
+};

uniqueId

@@ -1 +1 @@
-Tue Jan 21 2025 15:25:57 GMT+0000 (Coordinated Universal Time)
+Tue Jan 21 2025 15:51:57 GMT+0000 (Coordinated Universal Time)

utility/latest-versions.js

@@ -16,7 +16,7 @@ exports.latestVersions = {
     // As Angular CLI works with same minor versions of Angular Framework, a tilde match for the current
     Angular: '^19.1.0-next.0',
     NgPackagr: '^19.1.0-next.0',
-    DevkitBuildAngular: '^19.2.0-next.0+sha-197b770',
-    AngularBuild: '^19.2.0-next.0+sha-197b770',
-    AngularSSR: '^19.2.0-next.0+sha-197b770',
+    DevkitBuildAngular: '^19.2.0-next.0+sha-e01b4f6',
+    AngularBuild: '^19.2.0-next.0+sha-e01b4f6',
+    AngularSSR: '^19.2.0-next.0+sha-e01b4f6',
 };

web-worker/schema.d.ts

@@ -4,7 +4,7 @@
  * offloading computationally intensive tasks. This schematic generates the necessary files
  * for a new web worker and provides an optional code snippet to demonstrate its usage.
  */
-export interface Schema {
+export type Schema = {
     /**
      * The name for the new web worker. This will be used to create the worker file (e.g.,
      * `my-worker.worker.ts`).
@@ -24,4 +24,4 @@ export interface Schema {
      * Generate a code snippet that demonstrates how to create and use the new web worker.
      */
     snippet?: boolean;
-}
+};