Skip to content

Conversation

@angular-robot
Copy link
Contributor

@angular-robot angular-robot commented Oct 8, 2025

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@angular/animations (source) ^20.2.0^21.1.0-rc age adoption passing confidence
@angular/build 21.0.0-next.521.1.0-rc.0 age adoption passing confidence
@angular/build ^20.2.0^21.1.0-rc age adoption passing confidence
@angular/cdk 21.0.0-next.521.2.0-next.0 age adoption passing confidence
@angular/cdk ^20.2.0^21.2.0-next age adoption passing confidence
@angular/cli 21.0.0-next.521.1.0-rc.0 age adoption passing confidence
@angular/cli ^20.2.0^21.1.0-rc age adoption passing confidence
@angular/common (source) 21.0.0-next.521.1.0-rc.0 age adoption passing confidence
@angular/common (source) ^20.2.0^21.1.0-rc age adoption passing confidence
@angular/compiler (source) 21.0.0-next.521.1.0-rc.0 age adoption passing confidence
@angular/compiler (source) ^20.2.0^21.1.0-rc age adoption passing confidence
@angular/compiler-cli (source) 21.0.0-next.521.1.0-rc.0 age adoption passing confidence
@angular/compiler-cli (source) ^20.2.0^21.1.0-rc age adoption passing confidence
@angular/core (source) 21.0.0-next.521.1.0-rc.0 age adoption passing confidence
@angular/core (source) ^20.2.0^21.1.0-rc age adoption passing confidence
@angular/forms (source) 21.0.0-next.521.1.0-rc.0 age adoption passing confidence
@angular/forms (source) ^20.2.0^21.1.0-rc age adoption passing confidence
@angular/material ^20.2.0^21.2.0-next age adoption passing confidence
@angular/platform-browser (source) 21.0.0-next.521.1.0-rc.0 age adoption passing confidence
@angular/platform-browser (source) ^20.2.0^21.1.0-rc age adoption passing confidence
@angular/platform-server (source) 21.0.0-next.521.1.0-rc.0 age adoption passing confidence
@angular/router (source) 21.0.0-next.521.1.0-rc.0 age adoption passing confidence
@angular/router (source) ^20.2.0^21.1.0-rc age adoption passing confidence
@angular/ssr 21.0.0-next.521.1.0-rc.0 age adoption passing confidence

Release Notes

angular/angular (@​angular/animations)

v21.1.0-rc.0: 21.1.0-rc.0

Compare Source

common
Commit Description
feat - d8790972be Add custom transformations for Cloudflare and Cloudinary image loaders
feat - a6b8cb68af support custom transformations in ImageKit and Imgix loaders
compiler
Commit Description
feat - 640693da8e Add support for multiple swich cases matching
fix - 10da2f9029 better types for a few expression AST nodes
fix - 3a56c1367f produce accurate span for typeof and void expressions
fix - 76fa180005 provide location information for literal map keys
fix - fa7cb4b87a stop ThisReceiver inheritance from ImplicitReceiver
fix - 0ad3adc7c6 Support empty cases
compiler-cli
Commit Description
fix - 106ba63650 ensure component import diagnostics are reported within the imports expression
fix - 3a26244d61 fix up spelling of diagnostic
fix - f12e160bc1 support qualified names in typeof type references
core
Commit Description
feat - 99ad18a4ee Add stability debugging utility
feat - a0dfa5fa86 support rest arguments in function calls
feat - 6e18fa8bc9 support spread elements in array literals
feat - e407280ab5 support spread expressions in object literals
fix - 80b0fbba1f avoid leaking view data in animations
fix - e2a9938c51 explicitly cast signal node value to String
fix - 30e9c62bdf fix memory leak with event replay
fix - 86dc1283e8 handle cancelled traversals in fake navigation
fix - 91dc91bae4 sanitize sensitive attributes on SVG script elements
forms
Commit Description
feat - 2d85ae5811 add [formField] directive
fix - 89c37f1f7f allow custom controls to require dirty input
fix - 82edf18427 allow custom controls to require hidden input
fix - 1a4c3eb1d0 allow custom controls to require pending input
fix - e7d99f02cb clean up abort listener after timeout
fix - cb09fb8308 support custom controls with non signal-based models
fix - 282220d032 Support readonly arrays in signal forms
router
Commit Description
feat - 5edceffd04 add controls for route cleanup
feat - e44839b016 Add standalone function to create a comptued for isActive
feat - 1c00ab42f8 extend paramters of RedirectFunction to include paramMap and queryParamMap
feat - 7003e8d241 Publish Router's integration with platform Navigation API as experimental
fix - bcef77d950 Fix RouterLink href not updating with queryParamsHandling
fix - 9e043decaf handle errors from view transition updateCallbackDone promise

v21.1.0-next.4: 21.1.0-next.4

Compare Source

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

v21.1.0-next.3: 21.1.0-next.3

Compare Source

core
Commit Description
fix - 4f6014a756a avoid false-positive deprecation when using InjectionToken with factory only
forms
Commit Description
fix - d0097f7d0c2 fix signal forms type error

v21.1.0-next.2: 21.1.0-next.2

Compare Source

compiler
Commit Description
perf - ae1c0dc4900 chain query creation instructions
compiler-cli
Commit Description
fix - 8a3f3a91cf6 expand type for native controls with a dynamic type
forms
Commit Description
feat - aff8b248b35 expose element on signal forms Field directive
feat - ebc5c2b083a redo the signal forms metadata API
fix - 9fe95665813 add signals for dirty, hidden, and pending states in custom controls
fix - 14713d09923 allow resetting with empty string
fix - b96f65a963f memoize reads of child fields in signal forms (#​65802)
fix - 179b4cba67b Reuse key in parent in compat structure
upgrade
Commit Description
refactor - 75fe8f8af94 deprecate VERSION export
Deprecations
upgrade
  • VERSION from @angular/upgrade is deprecated. Please use the entry from @angular/upgrade/static instead.

v21.1.0-next.1

Compare Source

compiler
Commit Description
fix - 1c6b0704fb prevent XSS via SVG animation attributeName and MathML/SVG URLs
compiler-cli
Commit Description
fix - e30e61b789 avoid allocating an object for signals in production mode
fix - 6773d3b97d check that field radio button values are strings
core
Commit Description
fix - d8ab83ca82 run animation queue in environment injector context
fix - 886cf6c452 unable to inject viewProviders when host directive with providers is present
perf - e6d5632a30 tree shake unused dynamic [field] binding instructions (#​65599)
forms
Commit Description
feat - 7d1e502345 Allows transforms on FormUiControl signals
fix - cd7ae7e2ce support dynamic [field] bindings (#​65599)
http
Commit Description
fix - 0659d11c85 enable XSRF protection for same-origin absolute URLs
router
Commit Description
fix - b74a0693f2 handle errors from view transition finished promise

v21.1.0-next.0

Compare Source

platform-browser
Commit Description
feat - ec9dc94cee add context to createApplication
feat - ab67988d2e resolve JIT resources in createApplication
router
Commit Description
feat - a03c82564d Add scroll behavior controls on router navigation
feat - c25d749d85 Execute RunGuardsAndResolvers function in injection context
feat - c84d372778 Support wildcard params with segments trailing (#​64737)

v21.0.9

Compare Source

forms
Commit Type Description
82d556a8fb fix Ensure the control instruction comes after the other bindings
0055f3cc79 fix Rename signal form [field] to [formField]
migrations
Commit Type Description
e4bfa5c9e7 fix prevent duplicate imports in common-to-standalone migration

v21.0.8

Compare Source

core
Commit Type Description
a6a2621bf9 fix fix memory leak with event replay
5239e471a1 fix handle cancelled traversals in fake navigation

v21.0.7

Compare Source

compiler
Commit Type Description
8e808740c9 fix better types for a few expression AST nodes
63b1cdcf70 fix produce accurate span for typeof and void expressions
3c3ae0cb64 fix provide location information for literal map keys
523dbaf1c3 fix stop ThisReceiver inheritance from ImplicitReceiver
compiler-cli
Commit Type Description
4d9c4567ed fix ensure component import diagnostics are reported within the imports expression
cd405685af fix fix up spelling of diagnostic
778460fcca fix support qualified names in typeof type references
core
Commit Type Description
7c74674eb0 fix avoid leaking view data in animations
0edbee4550 fix explicitly cast signal node value to String
f9c29572d2 fix sanitize sensitive attributes on SVG script elements
forms
Commit Type Description
e3fba182f9 feat add [formField] directive
561772b152 fix allow custom controls to require dirty input
f0fb1d8581 fix allow custom controls to require hidden input
ec110f170b fix allow custom controls to require pending input
ae1dc16bb0 fix clean up abort listener after timeout
9748b0d5da fix support custom controls with non signal-based models
6bd22df987 fix Support readonly arrays in signal forms
router
Commit Type Description
41cd4a6af8 fix Fix RouterLink href not updating with queryParamsHandling
5e9e09aee0 fix handle errors from view transition updateCallbackDone promise

v21.0.6

Compare Source

Breaking Changes (affecting only experimental features)

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()
      }
    })
    

    (cherry picked from commit 348f149)

  • (cherry picked from commit ae0c590)

core
Commit Type Description
4c8fb3631d fix throw better errors for potential circular references
48492524ea fix use mutable ResponseInit type for RESPONSE_INIT token
forms
Commit Type Description
81772b420d feat pass field directive to class config
729b96476b refactor rename field to fieldTree in FieldContext and ValidationError
language-service
Commit Type Description
e0694df3ec fix avoid interpolation highlighting inside @​let
5047be4bc1 fix Prevent language service from crashing on suggestion diagnostic errors

v21.0.5

Compare Source

core
Commit Type Description

@angular-robot angular-robot force-pushed the ng-renovate/cross-repo-angular-dependencies branch 3 times, most recently from 573605a to 1bb1956 Compare October 13, 2025 10:04
@angular-robot angular-robot force-pushed the ng-renovate/cross-repo-angular-dependencies branch 4 times, most recently from cf1774b to 33fcd87 Compare October 21, 2025 14:36
@angular-robot angular-robot force-pushed the ng-renovate/cross-repo-angular-dependencies branch 5 times, most recently from 6753804 to e9d2fbf Compare October 29, 2025 18:05
@angular-robot angular-robot force-pushed the ng-renovate/cross-repo-angular-dependencies branch 3 times, most recently from e8c3ee9 to 45a29c8 Compare October 31, 2025 17:05
@angular-robot angular-robot changed the title build: update cross-repo angular dependencies build: update cross-repo angular dependencies to v21 Oct 31, 2025
@angular-robot angular-robot force-pushed the ng-renovate/cross-repo-angular-dependencies branch from 45a29c8 to cb190e8 Compare November 5, 2025 15:04
@angular-robot angular-robot changed the title build: update cross-repo angular dependencies to v21 build: update cross-repo angular dependencies Nov 5, 2025
@angular-robot angular-robot force-pushed the ng-renovate/cross-repo-angular-dependencies branch 3 times, most recently from d0cb1b3 to 51c661a Compare November 6, 2025 21:04
@angular-robot angular-robot changed the title build: update cross-repo angular dependencies build: update cross-repo angular dependencies to v21 Nov 6, 2025
@angular-robot angular-robot force-pushed the ng-renovate/cross-repo-angular-dependencies branch 2 times, most recently from 6890171 to 50e488b Compare November 12, 2025 16:41
@angular-robot angular-robot changed the title build: update cross-repo angular dependencies to v21 build: update cross-repo angular dependencies Nov 12, 2025
@angular-robot
Copy link
Contributor Author

angular-robot commented Nov 12, 2025

⚠️ Artifact update problem

Renovate failed to update artifacts 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: pnpm-lock.yaml
Scope: all 2 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
/tmp/renovate/repos/github/angular/web-codegen-scorer/report-app:
 ERR_PNPM_NO_MATURE_MATCHING_VERSION  Version 21.2.0-next.0 (released 11 minutes ago) of @angular/cdk does not meet the minimumReleaseAge constraint

This error happened while installing a direct dependency of /tmp/renovate/repos/github/angular/web-codegen-scorer/report-app

The latest release of @angular/cdk is "21.1.0". Published at 1/14/2026 3:26:57 PM

Other releases are:
  * v11-lts: 11.2.13 published at 5/19/2021
  * v12-lts: 12.2.13 published at 11/11/2021
  * v13-lts: 13.3.9 published at 6/2/2022
  * v14-lts: 14.2.7 published at 11/9/2022
  * v15-lts: 15.2.9 published at 5/3/2023
  * v16-lts: 16.2.14 published at 2/1/2024
  * v17-lts: 17.3.10 published at 5/22/2024
  * v18-lts: 18.2.14 published at 11/19/2024
  * v19-lts: 19.2.19 published at 6/25/2025
  * v20-lts: 20.2.14 published at 11/19/2025
  * next: 21.2.0-next.0 published at 1/14/2026 3:30:05 PM

If you need the full list of all 642 published versions run "$ pnpm view @angular/cdk versions".

If you want to install the matched version ignoring the time it was published, you can add the package name to the minimumReleaseAgeExclude setting. Read more about it: https://pnpm.io/settings#minimumreleaseageexclude

File name: examples/environments/angular/project/package.json
Command failed: /bin/sh -c bazel mod deps --lockfile_mode=update
WARNING: Invoking Bazel in batch mode since it is not invoked from within a workspace (below a directory having a MODULE.bazel file).
OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were deprecated in JDK 13 and will likely be removed in a future release.
ERROR: The 'mod' command is only supported from within a workspace (below a directory having a MODULE.bazel file).
See documentation at https://bazel.build/concepts/build-ref#workspace

File name: report-app/package.json
Command failed: /bin/sh -c bazel mod deps --lockfile_mode=update
WARNING: Invoking Bazel in batch mode since it is not invoked from within a workspace (below a directory having a MODULE.bazel file).
OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were deprecated in JDK 13 and will likely be removed in a future release.
ERROR: The 'mod' command is only supported from within a workspace (below a directory having a MODULE.bazel file).
See documentation at https://bazel.build/concepts/build-ref#workspace

File name: examples/environments/angular/project/package.json
Command failed: /bin/sh -c bazel mod deps --lockfile_mode=update
WARNING: Invoking Bazel in batch mode since it is not invoked from within a workspace (below a directory having a MODULE.bazel file).
OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were deprecated in JDK 13 and will likely be removed in a future release.
ERROR: The 'mod' command is only supported from within a workspace (below a directory having a MODULE.bazel file).
See documentation at https://bazel.build/concepts/build-ref#workspace

File name: report-app/package.json
Command failed: /bin/sh -c bazel mod deps --lockfile_mode=update
WARNING: Invoking Bazel in batch mode since it is not invoked from within a workspace (below a directory having a MODULE.bazel file).
OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were deprecated in JDK 13 and will likely be removed in a future release.
ERROR: The 'mod' command is only supported from within a workspace (below a directory having a MODULE.bazel file).
See documentation at https://bazel.build/concepts/build-ref#workspace

File name: examples/environments/angular/project/package.json
Command failed: /bin/sh -c bazel mod deps --lockfile_mode=update
WARNING: Invoking Bazel in batch mode since it is not invoked from within a workspace (below a directory having a MODULE.bazel file).
OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were deprecated in JDK 13 and will likely be removed in a future release.
ERROR: The 'mod' command is only supported from within a workspace (below a directory having a MODULE.bazel file).
See documentation at https://bazel.build/concepts/build-ref#workspace

File name: report-app/package.json
Command failed: /bin/sh -c bazel mod deps --lockfile_mode=update
WARNING: Invoking Bazel in batch mode since it is not invoked from within a workspace (below a directory having a MODULE.bazel file).
OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were deprecated in JDK 13 and will likely be removed in a future release.
ERROR: The 'mod' command is only supported from within a workspace (below a directory having a MODULE.bazel file).
See documentation at https://bazel.build/concepts/build-ref#workspace

File name: examples/environments/angular/project/package.json
Command failed: /bin/sh -c bazel mod deps --lockfile_mode=update
WARNING: Invoking Bazel in batch mode since it is not invoked from within a workspace (below a directory having a MODULE.bazel file).
OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were deprecated in JDK 13 and will likely be removed in a future release.
ERROR: The 'mod' command is only supported from within a workspace (below a directory having a MODULE.bazel file).
See documentation at https://bazel.build/concepts/build-ref#workspace

File name: report-app/package.json
Command failed: /bin/sh -c bazel mod deps --lockfile_mode=update
WARNING: Invoking Bazel in batch mode since it is not invoked from within a workspace (below a directory having a MODULE.bazel file).
OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were deprecated in JDK 13 and will likely be removed in a future release.
ERROR: The 'mod' command is only supported from within a workspace (below a directory having a MODULE.bazel file).
See documentation at https://bazel.build/concepts/build-ref#workspace

File name: examples/environments/angular/project/package.json
Command failed: /bin/sh -c bazel mod deps --lockfile_mode=update
WARNING: Invoking Bazel in batch mode since it is not invoked from within a workspace (below a directory having a MODULE.bazel file).
OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were deprecated in JDK 13 and will likely be removed in a future release.
ERROR: The 'mod' command is only supported from within a workspace (below a directory having a MODULE.bazel file).
See documentation at https://bazel.build/concepts/build-ref#workspace

File name: report-app/package.json
Command failed: /bin/sh -c bazel mod deps --lockfile_mode=update
WARNING: Invoking Bazel in batch mode since it is not invoked from within a workspace (below a directory having a MODULE.bazel file).
OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were deprecated in JDK 13 and will likely be removed in a future release.
ERROR: The 'mod' command is only supported from within a workspace (below a directory having a MODULE.bazel file).
See documentation at https://bazel.build/concepts/build-ref#workspace

File name: examples/environments/angular/project/package.json
Command failed: /bin/sh -c bazel mod deps --lockfile_mode=update
WARNING: Invoking Bazel in batch mode since it is not invoked from within a workspace (below a directory having a MODULE.bazel file).
OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were deprecated in JDK 13 and will likely be removed in a future release.
ERROR: The 'mod' command is only supported from within a workspace (below a directory having a MODULE.bazel file).
See documentation at https://bazel.build/concepts/build-ref#workspace

File name: report-app/package.json
Command failed: /bin/sh -c bazel mod deps --lockfile_mode=update
WARNING: Invoking Bazel in batch mode since it is not invoked from within a workspace (below a directory having a MODULE.bazel file).
OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were deprecated in JDK 13 and will likely be removed in a future release.
ERROR: The 'mod' command is only supported from within a workspace (below a directory having a MODULE.bazel file).
See documentation at https://bazel.build/concepts/build-ref#workspace

File name: examples/environments/angular/project/package.json
Command failed: /bin/sh -c bazel mod deps --lockfile_mode=update
WARNING: Invoking Bazel in batch mode since it is not invoked from within a workspace (below a directory having a MODULE.bazel file).
OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were deprecated in JDK 13 and will likely be removed in a future release.
ERROR: The 'mod' command is only supported from within a workspace (below a directory having a MODULE.bazel file).
See documentation at https://bazel.build/concepts/build-ref#workspace

File name: report-app/package.json
Command failed: /bin/sh -c bazel mod deps --lockfile_mode=update
WARNING: Invoking Bazel in batch mode since it is not invoked from within a workspace (below a directory having a MODULE.bazel file).
OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were deprecated in JDK 13 and will likely be removed in a future release.
ERROR: The 'mod' command is only supported from within a workspace (below a directory having a MODULE.bazel file).
See documentation at https://bazel.build/concepts/build-ref#workspace

File name: examples/environments/angular/project/package.json
Command failed: /bin/sh -c bazel mod deps --lockfile_mode=update
WARNING: Invoking Bazel in batch mode since it is not invoked from within a workspace (below a directory having a MODULE.bazel file).
OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were deprecated in JDK 13 and will likely be removed in a future release.
ERROR: The 'mod' command is only supported from within a workspace (below a directory having a MODULE.bazel file).
See documentation at https://bazel.build/concepts/build-ref#workspace

File name: report-app/package.json
Command failed: /bin/sh -c bazel mod deps --lockfile_mode=update
WARNING: Invoking Bazel in batch mode since it is not invoked from within a workspace (below a directory having a MODULE.bazel file).
OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were deprecated in JDK 13 and will likely be removed in a future release.
ERROR: The 'mod' command is only supported from within a workspace (below a directory having a MODULE.bazel file).
See documentation at https://bazel.build/concepts/build-ref#workspace

File name: examples/environments/angular/project/package.json
Command failed: /bin/sh -c bazel mod deps --lockfile_mode=update
WARNING: Invoking Bazel in batch mode since it is not invoked from within a workspace (below a directory having a MODULE.bazel file).
OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were deprecated in JDK 13 and will likely be removed in a future release.
ERROR: The 'mod' command is only supported from within a workspace (below a directory having a MODULE.bazel file).
See documentation at https://bazel.build/concepts/build-ref#workspace

File name: examples/environments/angular/project/package.json
Command failed: /bin/sh -c bazel mod deps --lockfile_mode=update
WARNING: Invoking Bazel in batch mode since it is not invoked from within a workspace (below a directory having a MODULE.bazel file).
OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were deprecated in JDK 13 and will likely be removed in a future release.
ERROR: The 'mod' command is only supported from within a workspace (below a directory having a MODULE.bazel file).
See documentation at https://bazel.build/concepts/build-ref#workspace

File name: report-app/package.json
Command failed: /bin/sh -c bazel mod deps --lockfile_mode=update
WARNING: Invoking Bazel in batch mode since it is not invoked from within a workspace (below a directory having a MODULE.bazel file).
OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were deprecated in JDK 13 and will likely be removed in a future release.
ERROR: The 'mod' command is only supported from within a workspace (below a directory having a MODULE.bazel file).
See documentation at https://bazel.build/concepts/build-ref#workspace

File name: examples/environments/angular/project/package.json
Command failed: /bin/sh -c bazel mod deps --lockfile_mode=update
WARNING: Invoking Bazel in batch mode since it is not invoked from within a workspace (below a directory having a MODULE.bazel file).
OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were deprecated in JDK 13 and will likely be removed in a future release.
ERROR: The 'mod' command is only supported from within a workspace (below a directory having a MODULE.bazel file).
See documentation at https://bazel.build/concepts/build-ref#workspace

File name: report-app/package.json
Command failed: /bin/sh -c bazel mod deps --lockfile_mode=update
WARNING: Invoking Bazel in batch mode since it is not invoked from within a workspace (below a directory having a MODULE.bazel file).
OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were deprecated in JDK 13 and will likely be removed in a future release.
ERROR: The 'mod' command is only supported from within a workspace (below a directory having a MODULE.bazel file).
See documentation at https://bazel.build/concepts/build-ref#workspace

File name: report-app/package.json
Command failed: /bin/sh -c bazel mod deps --lockfile_mode=update
WARNING: Invoking Bazel in batch mode since it is not invoked from within a workspace (below a directory having a MODULE.bazel file).
OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were deprecated in JDK 13 and will likely be removed in a future release.
ERROR: The 'mod' command is only supported from within a workspace (below a directory having a MODULE.bazel file).
See documentation at https://bazel.build/concepts/build-ref#workspace

File name: examples/environments/angular/project/package.json
Command failed: /bin/sh -c bazel mod deps --lockfile_mode=update
WARNING: Invoking Bazel in batch mode since it is not invoked from within a workspace (below a directory having a MODULE.bazel file).
OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were deprecated in JDK 13 and will likely be removed in a future release.
ERROR: The 'mod' command is only supported from within a workspace (below a directory having a MODULE.bazel file).
See documentation at https://bazel.build/concepts/build-ref#workspace

File name: report-app/package.json
Command failed: /bin/sh -c bazel mod deps --lockfile_mode=update
WARNING: Invoking Bazel in batch mode since it is not invoked from within a workspace (below a directory having a MODULE.bazel file).
OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were deprecated in JDK 13 and will likely be removed in a future release.
ERROR: The 'mod' command is only supported from within a workspace (below a directory having a MODULE.bazel file).
See documentation at https://bazel.build/concepts/build-ref#workspace

@angular-robot angular-robot force-pushed the ng-renovate/cross-repo-angular-dependencies branch from 50e488b to dad91c1 Compare November 12, 2025 17:04
@angular-robot angular-robot force-pushed the ng-renovate/cross-repo-angular-dependencies branch 3 times, most recently from 89e4ec2 to 7b7033e Compare November 19, 2025 20:04
@angular-robot angular-robot changed the title build: update cross-repo angular dependencies build: update cross-repo angular dependencies to v21 Nov 19, 2025
@angular-robot angular-robot force-pushed the ng-renovate/cross-repo-angular-dependencies branch from 7b7033e to 5c6720d Compare November 25, 2025 20:37
@angular-robot angular-robot changed the title build: update cross-repo angular dependencies to v21 build: update cross-repo angular dependencies Nov 25, 2025
@angular-robot angular-robot force-pushed the ng-renovate/cross-repo-angular-dependencies branch 2 times, most recently from 3f58c94 to 352ebbf Compare November 26, 2025 17:36
@angular-robot angular-robot changed the title build: update cross-repo angular dependencies build: update cross-repo angular dependencies to v21 Nov 26, 2025
@angular-robot angular-robot force-pushed the ng-renovate/cross-repo-angular-dependencies branch from 352ebbf to 93b6779 Compare December 3, 2025 14:39
@angular-robot angular-robot changed the title build: update cross-repo angular dependencies to v21 build: update cross-repo angular dependencies Dec 3, 2025
@angular-robot angular-robot force-pushed the ng-renovate/cross-repo-angular-dependencies branch 2 times, most recently from 73782d4 to 1429a7d Compare December 3, 2025 21:33
@angular-robot angular-robot changed the title build: update cross-repo angular dependencies build: update cross-repo angular dependencies to v21 Dec 3, 2025
@angular-robot angular-robot force-pushed the ng-renovate/cross-repo-angular-dependencies branch from 1429a7d to 8fcfe4e Compare December 10, 2025 19:04
@angular-robot angular-robot changed the title build: update cross-repo angular dependencies to v21 build: update cross-repo angular dependencies Dec 10, 2025
@angular-robot angular-robot force-pushed the ng-renovate/cross-repo-angular-dependencies branch 2 times, most recently from 980947e to 5a65351 Compare December 11, 2025 01:32
@angular-robot angular-robot changed the title build: update cross-repo angular dependencies build: update cross-repo angular dependencies to v21 Dec 11, 2025
@angular-robot angular-robot force-pushed the ng-renovate/cross-repo-angular-dependencies branch from 5a65351 to 193af27 Compare December 12, 2025 00:14
@angular-robot angular-robot changed the title build: update cross-repo angular dependencies to v21 build: update cross-repo angular dependencies Dec 12, 2025
@angular-robot angular-robot force-pushed the ng-renovate/cross-repo-angular-dependencies branch 4 times, most recently from 3fed6e2 to c6c3230 Compare December 18, 2025 22:05
@angular-robot angular-robot force-pushed the ng-renovate/cross-repo-angular-dependencies branch 3 times, most recently from 3983e16 to eeac6b4 Compare January 8, 2026 23:04
See associated pull request for more information.
@angular-robot angular-robot force-pushed the ng-renovate/cross-repo-angular-dependencies branch from eeac6b4 to 762ca61 Compare January 14, 2026 15:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant