Skip to content

chore: anchor vite 8#4790

Merged
escapedcat merged 2 commits into
masterfrom
chore/anchor-vite-8
May 26, 2026
Merged

chore: anchor vite 8#4790
escapedcat merged 2 commits into
masterfrom
chore/anchor-vite-8

Conversation

@escapedcat

Copy link
Copy Markdown
Member

No description provided.

escapedcat and others added 2 commits May 25, 2026 12:49
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>
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>
@qodo-code-review

Copy link
Copy Markdown

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

@escapedcat escapedcat merged commit 9b65f91 into master May 26, 2026
24 of 25 checks passed
@escapedcat escapedcat deleted the chore/anchor-vite-8 branch May 26, 2026 09:40
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.

1 participant