Skip to content

chore(deps): lock file maintenance - #1034

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/lock-file-maintenance
Open

chore(deps): lock file maintenance#1034
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/lock-file-maintenance

Conversation

@renovate

@renovate renovate Bot commented Oct 1, 2022

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.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • On day 1 of the month, every 12 months (* * 1 */12 *)
  • 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 Mend Renovate using a curated preset maintained by Sanity. View repository job log here

@renovate renovate Bot added dependencies Pull requests that update a dependency file lockFileMaintenance labels Oct 1, 2022
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 3 times, most recently from 86f6f87 to a28d46a Compare March 9, 2023 19:50
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from a28d46a to 16d0170 Compare March 9, 2023 20:06
@renovate

renovate Bot commented Aug 10, 2025

Copy link
Copy Markdown
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: 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: smooth-scroll-into-view-if-needed@2.0.2
npm error Found: semantic-release@20.1.3
npm error node_modules/semantic-release
npm error   dev semantic-release@"^20.1.1" from the root project
npm error
npm error Could not resolve dependency:
npm error peer semantic-release@"^22.0.12 || ^23.0.2 || ^24.0.0" from @sanity/semantic-release-preset@4.1.8
npm error node_modules/@sanity/semantic-release-preset
npm error   dev @sanity/semantic-release-preset@"^4.0.0" 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 /runner/cache/others/npm/_logs/2026-07-24T15_13_12_348Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-07-24T15_13_12_348Z-debug-0.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file lockFileMaintenance

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants