Skip to content

chore(deps): lock file maintenance#698

Merged
fh1ch merged 1 commit into
mainfrom
renovate/lock-file-maintenance
Jun 10, 2026
Merged

chore(deps): lock file maintenance#698
fh1ch merged 1 commit into
mainfrom
renovate/lock-file-maintenance

Conversation

@renovate

@renovate renovate Bot commented Jun 1, 2026

Copy link
Copy Markdown

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: (in timezone Etc/UTC)

  • Branch creation
    • Between 12:00 AM and 03:59 AM, on day 1 of the month (* 0-3 1 * *)
  • 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 was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot requested a review from a team as a code owner June 1, 2026 03:52
@renovate renovate Bot added the dep-bump label Jun 1, 2026
@renovate

renovate Bot commented Jun 1, 2026

Copy link
Copy Markdown
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: projects/stackblitz/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 could not resolve
npm error
npm error While resolving: @angular/core@21.2.16
npm error Found: @angular/compiler@21.2.15
npm error node_modules/@angular/compiler
npm error   @angular/compiler@"^21.2.13" from the root project
npm error   peer @angular/compiler@"^21.0.0" from @angular/build@21.2.13
npm error   node_modules/@angular/build
npm error     dev @angular/build@"21.2.13" from the root project
npm error   1 more (@angular/compiler-cli)
npm error
npm error Could not resolve dependency:
npm error peerOptional @angular/compiler@"21.2.16" from @angular/core@21.2.16
npm error node_modules/@angular/core
npm error   @angular/core@"^21.2.13" from the root project
npm error   peer @angular/core@"21.2.16" from @angular/animations@21.2.16
npm error   node_modules/@angular/animations
npm error     @angular/animations@"^21.2.13" from the root project
npm error     1 more (@angular/platform-browser)
npm error   6 more (@angular/build, @angular/common, @angular/forms, ...)
npm error
npm error Conflicting peer dependency: @angular/compiler@21.2.16
npm error node_modules/@angular/compiler
npm error   peerOptional @angular/compiler@"21.2.16" from @angular/core@21.2.16
npm error   node_modules/@angular/core
npm error     @angular/core@"^21.2.13" from the root project
npm error     peer @angular/core@"21.2.16" from @angular/animations@21.2.16
npm error     node_modules/@angular/animations
npm error       @angular/animations@"^21.2.13" from the root project
npm error       1 more (@angular/platform-browser)
npm error     6 more (@angular/build, @angular/common, @angular/forms, ...)
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 /runner/cache/others/npm/_logs/2026-06-10T05_11_58_543Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-06-10T05_11_58_543Z-debug-0.log

@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 5a47e87 to 5539c56 Compare June 1, 2026 17:47
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 5539c56 to c3b4c48 Compare June 10, 2026 05:13
@spike-rabbit spike-rabbit force-pushed the renovate/lock-file-maintenance branch from c3b4c48 to 91c906c Compare June 10, 2026 13:40
@renovate

renovate Bot commented Jun 10, 2026

Copy link
Copy Markdown
Author

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@spike-rabbit spike-rabbit force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from 8a31aa0 to 91c46bd Compare June 10, 2026 14:08
@spike-rabbit spike-rabbit force-pushed the renovate/lock-file-maintenance branch from 91c46bd to e45d522 Compare June 10, 2026 14:10

@fh1ch fh1ch left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

LGTM 👍

@fh1ch fh1ch added this pull request to the merge queue Jun 10, 2026
Merged via the queue into main with commit cf00dff Jun 10, 2026
7 checks passed
@fh1ch fh1ch deleted the renovate/lock-file-maintenance branch June 10, 2026 14:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants