Skip to content

build: lock file maintenance (20.1.x) #62622

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: 20.1.x
Choose a base branch
from
Open

build: lock file maintenance (20.1.x) #62622

wants to merge 1 commit into from
+2,677 −1,409

Conversation

angular-robot
Copy link
Collaborator

@angular-robot angular-robot commented Jul 14, 2025 •
edited
Loading

This PR contains the following updates:

Update Change
lockFileMaintenance All locks refreshed

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

Configuration

📅 Schedule: Branch creation - "before 4am on monday" in timezone America/Tijuana, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

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

This PR has been generated by Renovate Bot.

@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: patch This PR is targeted for the next patch release labels Jul 14, 2025
@angular-robot
Copy link
Collaborator Author

angular-robot commented Jul 14, 2025 •
edited
Loading

⚠️ 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: modules/ssr-benchmarks/yarn.lock
warning ../package.json: No license field
error Package "" refers to a non-existing file '"/tmp/renovate/repos/github/angular/angular/dist/packages-dist/common"'.
File name: pnpm-lock.yaml
Scope: all 24 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
modules                                  |  WARN  deprecated protractor@7.0.0
.                                        |  WARN  deprecated @babel/plugin-proposal-async-generator-functions@7.20.7
.                                        |  WARN  deprecated gulp-conventional-changelog@5.0.0
.                                        |  WARN  deprecated angular@1.5.11
.                                        |  WARN  deprecated angular@1.6.10
.                                        |  WARN  deprecated angular@1.7.9
.                                        |  WARN  deprecated angular@1.8.3
.                                        |  WARN  deprecated tslint@6.1.3
Progress: resolved 191, reused 0, downloaded 0, added 0
Progress: resolved 202, reused 2, downloaded 0, added 0
Packages are hard linked from the content-addressable store to the virtual store.
  Content-addressable store is at: /tmp/renovate/cache/others/pnpm/store/v3
  Virtual store is at:             node_modules/.pnpm
Progress: resolved 320, reused 2, downloaded 1, added 0
Progress: resolved 620, reused 2, downloaded 1, added 0
Progress: resolved 1004, reused 2, downloaded 1, added 0
Progress: resolved 1440, reused 2, downloaded 1, added 0
Progress: resolved 1895, reused 2, downloaded 1, added 0
Progress: resolved 2358, reused 2, downloaded 1, added 0
 ERR_PNPM_NO_MATCHING_VERSION  No matching version found for @angular/common@0.0.0-PLACEHOLDER

This error happened while installing a direct dependency of /tmp/renovate/repos/github/angular/angular

The latest release of @angular/common is "20.1.2".

Other releases are:
  * v4-lts: 4.4.7
  * v5-lts: 5.2.11
  * v6-lts: 6.1.10
  * v7-lts: 7.2.15
  * v8-lts: 8.2.14
  * v9-lts: 9.1.13
  * v10-lts: 10.2.5
  * v11-lts: 11.2.14
  * v12-lts: 12.2.17
  * v14-lts: 14.3.0
  * v13-lts: 13.4.0
  * v15-lts: 15.2.10
  * v16-lts: 16.2.12
  * v17-lts: 17.3.12
  * v18-lts: 18.2.13
  * v19-lts: 19.2.14
  * next: 20.2.0-next.1

If you need the full list of all 930 published versions run "$ pnpm view @angular/common versions".
File name: undefined
Command failed: yarn bazel run //.github/actions/deploy-docs-site:main.update
Loading: 
Loading: 
Loading: 
Loading: 
Loading: 
Loading: 
Loading: 
Loading: 
Loading: 
Loading: 
Loading: 1 packages loaded
ERROR: Skipping '//.github/actions/deploy-docs-site:main.update': no such target '//.github/actions/deploy-docs-site:main.update': target 'main.update' not declared in package '.github/actions/deploy-docs-site' defined by /tmp/renovate/repos/github/angular/angular/.github/actions/deploy-docs-site/BUILD.bazel (Tip: use `query "//.github/actions/deploy-docs-site:*"` to see all the targets in that package)
WARNING: Target pattern parsing failed.
ERROR: no such target '//.github/actions/deploy-docs-site:main.update': target 'main.update' not declared in package '.github/actions/deploy-docs-site' defined by /tmp/renovate/repos/github/angular/angular/.github/actions/deploy-docs-site/BUILD.bazel (Tip: use `query "//.github/actions/deploy-docs-site:*"` to see all the targets in that package)
INFO: Elapsed time: 40.302s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (2 packages loaded)
ERROR: Build failed. Not running target
error Command failed with exit code 1.

@ngbot ngbot bot added this to the Backlog milestone Jul 14, 2025
@pullapprove pullapprove bot requested a review from devversion July 14, 2025 07:15
@thePunderWoman thePunderWoman removed the request for review from devversion July 14, 2025 15:00
@angular-robot angular-robot force-pushed the ng-renovate/20.1.x-lock-file-maintenance branch 2 times, most recently from d2d31b9 to f87b697 Compare July 14, 2025 19:43
@AndrewKushnir AndrewKushnir added the action: cleanup The PR is in need of cleanup, either due to needing a rebase or in response to comments from reviews label Jul 14, 2025
@angular-robot angular-robot force-pushed the ng-renovate/20.1.x-lock-file-maintenance branch 4 times, most recently from 59052c7 to a48a260 Compare July 16, 2025 18:14
@angular-robot
build: lock file maintenance
0dd8249 
See associated pull request for more information.
@angular-robot angular-robot force-pushed the ng-renovate/20.1.x-lock-file-maintenance branch from a48a260 to 0dd8249 Compare July 17, 2025 22:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@thePunderWoman thePunderWoman thePunderWoman approved these changes

Assignees
No one assigned
Labels
action: cleanup The PR is in need of cleanup, either due to needing a rebase or in response to comments from reviews action: merge The PR is ready for merge by the caretaker area: build & ci Related the build and CI infrastructure of the project target: patch This PR is targeted for the next patch release
Projects
None yet
Milestone
Backlog
Development

Successfully merging this pull request may close these issues.
3 participants
@angular-robot @thePunderWoman @AndrewKushnir