Skip to content

Lock file maintenance - #35

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

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

Conversation

@renovate

@renovate renovate Bot commented Apr 20, 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 America/Los_Angeles)

  • Branch creation
    • Between 12:00 AM and 03:59 AM, only on Monday (* 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.

@vercel

vercel Bot commented Apr 20, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
isitout Ready Ready Preview, Comment Jul 28, 2026 7:10am

Request Review

@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from b712ebf to c1209fd Compare April 24, 2026 21:28
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from c1209fd to 09cf751 Compare April 29, 2026 16:36
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from 09cf751 to bf921f5 Compare May 5, 2026 18:45
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from bf921f5 to 4e46986 Compare May 18, 2026 11:53
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from 4e46986 to 860d25f Compare May 18, 2026 19:35
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from 860d25f to cd5573b Compare May 22, 2026 04:40
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from cd5573b to 460f088 Compare May 28, 2026 17:13
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from 460f088 to 1eb3f52 Compare June 1, 2026 18:55
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from 1eb3f52 to d3db5fe Compare June 11, 2026 12:58
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from d3db5fe to 034d579 Compare June 12, 2026 10:33
@renovate

renovate Bot commented Jun 12, 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 force-pushed the renovate/lock-file-maintenance branch from 910dbd5 to 416878b Compare June 26, 2026 15:45
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from 416878b to 0ca580d Compare June 27, 2026 05:57
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from 0ca580d to 64f360d Compare June 29, 2026 21:03
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from 64f360d to 4b41a90 Compare July 2, 2026 03:28
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from 4b41a90 to c6cd305 Compare July 3, 2026 01:30
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from c6cd305 to 9e6346b Compare July 3, 2026 14:53
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from 9e6346b to af62ed7 Compare July 4, 2026 01:47
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from af62ed7 to a9b41d1 Compare July 6, 2026 18:56
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from a9b41d1 to b6e83f8 Compare July 25, 2026 12:28
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from b6e83f8 to 60b0f99 Compare July 27, 2026 15:13
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from 60b0f99 to 5dc9873 Compare July 27, 2026 21:04
@renovate

renovate Bot commented Jul 30, 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 error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: convex-tutorial@0.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@"^8.0.0" from @vitejs/plugin-react@6.0.5
npm error node_modules/@vitejs/plugin-react
npm error   dev @vitejs/plugin-react@"6.0.5" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error 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-15T13_58_46_129Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-08-15T13_58_46_129Z-debug-0.log

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants