Skip to content

build: lock file maintenance (22.0.x)#68790

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

build: lock file maintenance (22.0.x)#68790
angular-robot wants to merge 1 commit into
angular:22.0.xfrom
angular-robot:ng-renovate/22.0.x-lock-file-maintenance

Conversation

@angular-robot
Copy link
Copy Markdown
Contributor

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

See associated pull request for more information.
@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 May 19, 2026
@angular-robot
Copy link
Copy Markdown
Contributor Author

⚠️ 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: adev/src/content/tutorials/signals/common/package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: angular.dev@0.0.0
npm error Found: typescript@5.9.3
npm error node_modules/typescript
npm error   dev typescript@"~5.9.3" from the root project
npm error
npm error Could not resolve dependency:
npm error peer typescript@">=6.0 <6.1" from @angular/build@22.0.0-rc.0
npm error node_modules/@angular/build
npm error   dev @angular/build@"^22.0.0-next" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2026-05-19T06_21_26_828Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2026-05-19T06_21_26_828Z-debug-0.log

File name: adev/src/content/tutorials/signal-forms/common/package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: angular.dev@0.0.0
npm error Found: typescript@5.9.3
npm error node_modules/typescript
npm error   dev typescript@"~5.9.3" from the root project
npm error
npm error Could not resolve dependency:
npm error peer typescript@">=6.0 <6.1" from @angular/build@22.0.0-rc.0
npm error node_modules/@angular/build
npm error   dev @angular/build@"^22.0.0-next" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2026-05-19T06_21_27_758Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2026-05-19T06_21_27_758Z-debug-0.log

File name: adev/src/content/tutorials/playground/common/package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: angular.dev@0.0.0
npm error Found: typescript@5.9.3
npm error node_modules/typescript
npm error   dev typescript@"~5.9.2" from the root project
npm error
npm error Could not resolve dependency:
npm error peer typescript@">=6.0 <6.1" from @angular/build@22.0.0-rc.0
npm error node_modules/@angular/build
npm error   dev @angular/build@"^22.0.0-next" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2026-05-19T06_21_28_690Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2026-05-19T06_21_28_690Z-debug-0.log

File name: adev/src/content/tutorials/learn-angular/common/package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: angular.dev@0.0.0
npm error Found: typescript@5.9.3
npm error node_modules/typescript
npm error   dev typescript@"~5.9.2" from the root project
npm error
npm error Could not resolve dependency:
npm error peer typescript@">=6.0 <6.1" from @angular/build@22.0.0-rc.0
npm error node_modules/@angular/build
npm error   dev @angular/build@"^22.0.0-next" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2026-05-19T06_21_29_717Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2026-05-19T06_21_29_717Z-debug-0.log

File name: adev/src/content/tutorials/homepage/package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: angular.dev@0.0.0
npm error Found: typescript@5.9.3
npm error node_modules/typescript
npm error   dev typescript@"~5.9.2" from the root project
npm error
npm error Could not resolve dependency:
npm error peer typescript@">=6.0 <6.1" from @angular/build@22.0.0-rc.0
npm error node_modules/@angular/build
npm error   dev @angular/build@"^22.0.0-next" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2026-05-19T06_21_30_654Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2026-05-19T06_21_30_654Z-debug-0.log

File name: adev/src/content/tutorials/first-app/common/package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: angular.dev@0.0.0
npm error Found: typescript@5.9.3
npm error node_modules/typescript
npm error   dev typescript@"~5.9.2" from the root project
npm error
npm error Could not resolve dependency:
npm error peer typescript@">=6.0 <6.1" from @angular/build@22.0.0-rc.0
npm error node_modules/@angular/build
npm error   dev @angular/build@"^22.0.0-next" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2026-05-19T06_21_31_563Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2026-05-19T06_21_31_563Z-debug-0.log

File name: adev/src/content/tutorials/deferrable-views/common/package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: angular.dev@0.0.0
npm error Found: typescript@5.9.3
npm error node_modules/typescript
npm error   dev typescript@"~5.9.2" from the root project
npm error
npm error Could not resolve dependency:
npm error peer typescript@">=6.0 <6.1" from @angular/build@22.0.0-rc.0
npm error node_modules/@angular/build
npm error   dev @angular/build@"^22.0.0-next" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2026-05-19T06_21_32_493Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2026-05-19T06_21_32_493Z-debug-0.log

@ngbot ngbot Bot added this to the Backlog milestone May 19, 2026
@pullapprove pullapprove Bot requested review from kirjs May 19, 2026 06:24
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