Skip to content

chore: lock file maintenance#4786

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

chore: lock file maintenance#4786
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/lock-file-maintenance

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented May 25, 2026

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
    • "before 5am on monday"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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.

@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch 3 times, most recently from 2cc4d4d to bc6a422 Compare May 26, 2026 08:50
escapedcat added a commit that referenced this pull request May 26, 2026
* chore: have renovate hold PRs for 3 days after release

Recent renovate PRs went red because freshly-published versions
weren't fully propagated on the npm registry / CDN. `minimumReleaseAge`
delays PRs until the version is at least three days old, and
`internalChecksFilter: "strict"` suppresses the PR entirely until
that window passes rather than opening it and blocking merge.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* chore: anchor vite to ^8 in root devDependencies

Without a root-level vite, pnpm peer-resolves vitest@4 against the
vite@5.4.21 that vitepress pulls in, which lacks the ./module-runner
subpath vitest needs and breaks lockfile-maintenance refreshes
(see PR #4786). Anchoring vite at ^8 (within vitest 4's declared peer
range of ^6 || ^7 || ^8) keeps the topology stable across regens
while vitepress retains its own scoped vite@5.

Also tightens the coverage `include` glob to *.{ts,js,mjs,cjs} so
vitest 4's uncovered-files pass under vite@8 stops trying to parse
commitlint.schema.json as JavaScript.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from d903feb to 8f4c5bd Compare May 26, 2026 09:44
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 8f4c5bd to cadc7b5 Compare May 26, 2026 09:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

0 participants