Skip to content

build: lock file maintenance (21.2.x)#32777

Open
angular-robot wants to merge 1 commit intoangular:21.2.xfrom
angular-robot:ng-renovate/21.2.x-lock-file-maintenance
Open

build: lock file maintenance (21.2.x)#32777
angular-robot wants to merge 1 commit intoangular:21.2.xfrom
angular-robot:ng-renovate/21.2.x-lock-file-maintenance

Conversation

@angular-robot
Copy link
Contributor

@angular-robot angular-robot commented Mar 17, 2026

This PR contains the following updates:

Update Change
lockFileMaintenance All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.


  • 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 Mar 17, 2026
Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request consists of automated lock file maintenance, refreshing the pnpm-lock.yaml to update various dependencies to their latest versions. This is a routine task to ensure the project benefits from the latest features and security patches. As the changes are confined to the lock file and do not involve any direct code modifications, there are no issues to report. The updates appear correct for their intended purpose.

@angular-robot angular-robot force-pushed the ng-renovate/21.2.x-lock-file-maintenance branch from 8940708 to e344576 Compare March 17, 2026 12:18
@angular angular deleted a comment from angular-robot Mar 17, 2026
See associated pull request for more information.
@angular-robot angular-robot force-pushed the ng-renovate/21.2.x-lock-file-maintenance branch from e344576 to 9f51b72 Compare March 17, 2026 12:32
@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.lock
Command failed: bazel mod deps
 no actions running
 no actions running
ERROR: Missing checksum for registry file https://bcr.bazel.build/modules/platforms/1.0.0/MODULE.bazel not permitted with --lockfile_mode=error. Please run `bazel mod deps --lockfile_mode=update` to update your lockfile.

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.

1 participant