Skip to content

build: lock file maintenance (20.0.x) #61814

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
Closed
wants to merge 1 commit into from
Closed

build: lock file maintenance (20.0.x) #61814

wants to merge 1 commit into from
+4,060 −3,989

Conversation

angular-robot
Copy link
Collaborator

@angular-robot angular-robot commented Jun 2, 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 labels Jun 2, 2025
@angular-robot
Copy link
Collaborator Author

angular-robot commented Jun 2, 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 17 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 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 protractor@7.0.0
.                                        |  WARN  deprecated tslint@6.1.3
Progress: resolved 177, reused 2, downloaded 0, added 0
Progress: resolved 189, reused 3, downloaded 0, added 0
Progress: resolved 452, reused 3, downloaded 0, added 0
Progress: resolved 914, reused 3, downloaded 0, added 0
Progress: resolved 1438, reused 3, downloaded 0, added 0
Progress: resolved 1922, reused 3, downloaded 0, added 0
Progress: resolved 2391, reused 3, downloaded 0, added 0
/tmp/renovate/repos/github/angular/angular/packages/core/test/bundling:
 ERR_PNPM_NO_MATCHING_VERSION  No matching version found for @angular/compiler@0.0.0-PLACEHOLDER

This error happened while installing a direct dependency of /tmp/renovate/repos/github/angular/angular/packages/core/test/bundling

The latest release of @angular/compiler is "20.0.0".

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
  * next: 20.0.0
  * v19-lts: 19.2.14

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

@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 labels Jun 2, 2025
@ngbot ngbot bot added this to the Backlog milestone Jun 2, 2025
@angular-robot angular-robot force-pushed the ng-renovate/20.0.x-lock-file-maintenance branch 2 times, most recently from 79e5f3c to 846a0ba Compare June 3, 2025 11:16
@thePunderWoman thePunderWoman added target: patch This PR is targeted for the next patch release merge: caretaker note Alert the caretaker performing the merge to check the PR for an out of normal action needed or note labels Jun 3, 2025
@thePunderWoman
Copy link
Contributor

Caretaker note: the lint failure is the typical license issue. This is safe to merge.

@angular-robot angular-robot force-pushed the ng-renovate/20.0.x-lock-file-maintenance branch from 846a0ba to 74b3337 Compare June 3, 2025 11:45
@angular-robot
build: lock file maintenance
ec81b41 
See associated pull request for more information.
@angular-robot angular-robot force-pushed the ng-renovate/20.0.x-lock-file-maintenance branch from 74b3337 to ec81b41 Compare June 3, 2025 12:54
@kirjs
Copy link
Contributor

kirjs commented Jun 3, 2025

This PR was merged into the repository by commit 661b58c.

The changes were merged into the following branches: 20.0.x

kirjs pushed a commit that referenced this pull request Jun 3, 2025
@angular-robot @kirjs
build: lock file maintenance (#61814)
661b58c 
See associated pull request for more information.

PR Close #61814
@kirjs kirjs closed this Jun 3, 2025
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: merge The PR is ready for merge by the caretaker area: build & ci Related the build and CI infrastructure of the project merge: caretaker note Alert the caretaker performing the merge to check the PR for an out of normal action needed or note PullApprove: disable 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 @kirjs