Skip to content

Conversation

@angular-robot
Copy link
Contributor

@angular-robot angular-robot commented Dec 15, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
@angular-devkit/build-angular 21.1.0-next.2 -> 21.1.0-next.3 age adoption passing confidence pnpm.catalog.default patch
@angular-devkit/core 21.1.0-next.2 -> 21.1.0-next.3 age adoption passing confidence pnpm.catalog.default patch
@angular-devkit/schematics 21.1.0-next.2 -> 21.1.0-next.3 age adoption passing confidence pnpm.catalog.default patch
@angular/build 21.1.0-next.2 -> 21.1.0-next.3 age adoption passing confidence pnpm.catalog.default patch
@angular/cli 21.1.0-next.2 -> 21.1.0-next.3 age adoption passing confidence pnpm.catalog.default patch
@angular/common (source) 21.1.0-next.3 -> 21.1.0-next.4 age adoption passing confidence pnpm.catalog.default patch
@angular/compiler (source) 21.1.0-next.3 -> 21.1.0-next.4 age adoption passing confidence pnpm.catalog.default patch
@angular/compiler-cli (source) 21.1.0-next.3 -> 21.1.0-next.4 age adoption passing confidence pnpm.catalog.default patch
@angular/core (source) 21.1.0-next.3 -> 21.1.0-next.4 age adoption passing confidence pnpm.catalog.default patch
@angular/forms (source) 21.1.0-next.3 -> 21.1.0-next.4 age adoption passing confidence pnpm.catalog.default patch
@angular/localize 21.1.0-next.3 -> 21.1.0-next.4 age adoption passing confidence pnpm.catalog.default patch
@angular/ng-dev 9549854 -> 82943a3 devDependencies digest
@angular/platform-browser (source) 21.1.0-next.3 -> 21.1.0-next.4 age adoption passing confidence pnpm.catalog.default patch
@angular/platform-browser-dynamic (source) 21.1.0-next.3 -> 21.1.0-next.4 age adoption passing confidence pnpm.catalog.default patch
@angular/platform-server (source) 21.1.0-next.3 -> 21.1.0-next.4 age adoption passing confidence pnpm.catalog.default patch
@angular/router (source) 21.1.0-next.3 -> 21.1.0-next.4 age adoption passing confidence pnpm.catalog.default patch
@angular/ssr 21.1.0-next.2 -> 21.1.0-next.3 age adoption passing confidence pnpm.catalog.default patch
@schematics/angular 21.1.0-next.2 -> 21.1.0-next.3 age adoption passing confidence pnpm.catalog.default patch
angular/dev-infra 54e4070 -> af87f27 action digest
devinfra 54e4070 -> af87f27 git_override digest

🔡 If you wish to disable git hash updates, add ":disableDigestUpdates" to the extends array in your config.


Release Notes

angular/angular-cli (@​angular-devkit/build-angular)

v21.1.0-next.3

Compare Source

@​angular/cli
Commit Type Description
348096623 fix enhance list_projects MCP tool file system traversal and symlink handling
032257a6d fix improve signal forms lesson examples in AI tutor
18d74dde8 fix rename mcp devserver tools to comply with naming spec
a15db28b2 perf cache resolved specific version in package manager abstraction
@​schematics/angular
Commit Type Description
52ace04a7 fix improve VS Code background compilation start/end detection
288a9225c fix remove inlineSources from library tsconfig template
@​angular/build
Commit Type Description
98c207bc0 fix add browser condition to resolver for vitest
f39f7ee95 fix allow non-prefixed requests when using SSR and base href
7c7e6a614 fix conditionally manage Vitest UI option
edeb41c0e fix ensure tests run when compilation error is resolved
9744af1f8 fix remove LmdbCacheStore export from private API
@​angular/ssr
Commit Type Description
e5651224b fix add leading slash to well-known non-Angular URLs
081e31337 fix propagate status code to redirect
2d56a319d fix skip SSR processing for well-known non-Angular URLs like favicon.ico
angular/angular (@​angular/common)

v21.1.0-next.4

Compare Source

Breaking Changes

forms
  • The shape of SignalFormsConfig.classes has changed

    Previously each function in the classes map took a FieldState. Now
    it takes a Field directive.

    For example if you previously had:

    provideSignalFormsConfig({
      classes: {
        'my-valid': (state) => state.valid()
      }
    })
    

    You would need to update to:

    provideSignalFormsConfig({
      classes: {
        'my-valid': ({state}) => state().valid()
      }
    })
    
core
Commit Type Description
06be8034bb fix Microtask scheduling should be used after any application synchronization
b4f584cf42 fix return StaticProvider for providePlatformInitializer
7be4ddef1c fix throw better errors for potential circular references
f516370c8e fix use mutable ResponseInit type for RESPONSE_INIT token
forms
Commit Type Description
348f149e8b feat pass field directive to class config
ae0c59028a refactor rename field to fieldTree in FieldContext and ValidationError
language-service
Commit Type Description
9f5744a92d fix avoid interpolation highlighting inside @​let
ce1a4769f9 fix Prevent language service from crashing on suggestion diagnostic errors

  • If you want to rebase/retry this PR, check this box

@angular-robot angular-robot added action: merge The PR is ready for merge by the caretaker area: build & ci Related the build and CI infrastructure of the project target: automation This PR is targeted to only merge into the branch defined in Github [bot use only] labels Dec 15, 2025
@angular-robot angular-robot force-pushed the ng-renovate/main-cross-repo-angular-dependencies branch 2 times, most recently from 84f6adb to 085dd83 Compare December 16, 2025 16:44
@angular-robot angular-robot force-pushed the ng-renovate/main-cross-repo-angular-dependencies branch 11 times, most recently from 81de5c8 to 649e7b6 Compare December 22, 2025 16:41
See associated pull request for more information.
@angular-robot angular-robot force-pushed the ng-renovate/main-cross-repo-angular-dependencies branch from 649e7b6 to 0f40863 Compare December 26, 2025 17:05
@angular-robot
Copy link
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: MODULE.bazel
Command failed: bazel mod deps --lockfile_mode=update
2025/12/26 17:05:14 Downloading https://releases.bazel.build/8.5.0/release/bazel-8.5.0-linux-x86_64...
2025/12/26 17:05:30 could not download Bazel: failed to download bazel: failed to download bazel: HTTP GET https://releases.bazel.build/8.5.0/release/bazel-8.5.0-linux-x86_64 failed: unable to complete 5 requests to https://releases.bazel.build/8.5.0/release/bazel-8.5.0-linux-x86_64 within 30s. Most recent failure: Get "https://releases.bazel.build/8.5.0/release/bazel-8.5.0-linux-x86_64": tls: failed to verify certificate: x509: certificate has expired or is not yet valid: current time 2025-12-26T17:05:30Z is after 2025-12-26T08:35:39Z

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

action: merge The PR is ready for merge by the caretaker area: build & ci Related the build and CI infrastructure of the project target: automation This PR is targeted to only merge into the branch defined in Github [bot use only]

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants