Skip to content

chore(deps): lock file maintenance - #1678

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

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

Conversation

@renovate

@renovate renovate Bot commented Feb 15, 2026

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: (in timezone Asia/Tokyo)

  • Branch creation
    • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, 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.

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Feb 15, 2026

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Preview URL Updated (UTC)
✅ Deployment successful!
View logs
astraea b080bd5 Commit Preview URL

Branch Preview URL
Aug 09 2026, 04:35 PM

@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 19 times, most recently from eb3b068 to 34dedf9 Compare February 23, 2026 18:14
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 6 times, most recently from b0a2543 to 072e799 Compare February 26, 2026 05:42
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 12 times, most recently from eb4f75a to 65b2dc5 Compare March 11, 2026 21:50
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 7 times, most recently from c6686d9 to cdfb840 Compare March 19, 2026 05:07
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 8 times, most recently from 36f30d1 to 796971f Compare March 26, 2026 14:55
@renovate

renovate Bot commented May 14, 2026

Copy link
Copy Markdown
Contributor Author

ℹ️ Artifact update notice

File name: package-lock.json

npm --before could not be enforced because existing locked packages were published after the minimumReleaseAge cutoff. This will resolve after the next lock file maintenance run.

@renovate

renovate Bot commented Aug 9, 2026

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: astraea@5.0.0
npm error Found: vite@undefined
npm error node_modules/vite
npm error   dev vite@"8.2.1" from the root project
npm error
npm error Could not resolve dependency:
npm error peer vite@"^5.2.0 || ^6 || ^7 || ^8" from @tailwindcss/vite@4.3.3
npm error node_modules/@tailwindcss/vite
npm error   @tailwindcss/vite@"^4.3.3" 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-08-10T09_59_04_210Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-08-10T09_59_04_210Z-debug-0.log

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants