Repository navigation
Bump vitest from 4.1.11 to 5.0.4 - #715
Merged
Merged
Conversation
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 4.1.11 to 5.0.4. - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md) - [Commits](https://github.com/vitest-dev/vitest/commits/v5.0.4/packages/vitest) --- updated-dependencies: - dependency-name: vitest dependency-version: 5.0.4 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
the
dependencies
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
cursor Bot
pushed a commit
that referenced
this pull request
Oct 15, 2026
<!-- CURSOR_AGENT_PR_BODY_BEGIN --> Restore `bun install --frozen-lockfile` after sequential Dependabot merges left unused vitest 4.1.11 packages in `bun.lock`, and run Worker tests on vitest 5.0.4. ## Why [#404](#404) reports the latest benchmarks-mode refresh as unhealthy: [run 38742460171](https://github.com/hraness/aicharts/actions/runs/38742460171) failed at `DEPENDENCIES_OUTCOME=failure` with bun 1.3.14’s “lockfile had changes, but lockfile is frozen.” Every source was skipped. That SHA already included Dependabot #713–#715. Each PR updated `package.json` and `bun.lock` on its own, but the merged lockfile still listed vitest 4.1.11 packages that bun now wants to prune (`@vitest/pretty-format`, `@vitest/runner`, `@vitest/snapshot`, `@vitest/utils`, `tinyrainbow`, and `@vitest/snapshot/magic-string`). Frozen install treats that prune as a lockfile change. #715 also left Worker / Worker gates red: vitest 5.0.4 turns `fsModuleCache` on by default, and `@cloudflare/vitest-plugin` 1.4.0’s workerd runner fails every file with `readAll` ENOENT on `node_modules/.vitest-cache` ([cloudflare/workers-sdk#16237](cloudflare/workers-sdk#16237)). ## Change - Regenerated `bun.lock` with bun 1.3.14 (the version CI and `packageManager` pin). Twelve stale vitest 4 lines removed. `package.json` is unchanged. - `--frozen-lockfile` is still required; this does not weaken CI. - Set `fsModuleCache: false` in the Worker vitest config so tests run on vitest 5.0.4. Vitest is not downgraded. ## Verification - `bun install --frozen-lockfile` failed on a clean checkout of `de653a7` (then-current `main`). - After the lockfile prune, the same command succeeded on a clean `node_modules` tree, in an isolated temp directory, in CI Checks, and on the Vercel preview install. - `bun run usage:worker:check`: 43 files, 733 tests passed on vitest 5.0.4. Cargo / rustls is out of scope (handled separately). #404 <!-- CURSOR_AGENT_PR_BODY_END --> <div><a href="https://cursor.com/agents/bc-0e96a653-591b-503c-85c3-12515546a681?cursor_ref=pr_footer&cursor_cta=open_in_web"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-web-light.png"><img alt="Open in Web" width="114" height="28" src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a> <a href="https://cursor.com/background-agent?bcId=bc-0e96a653-591b-503c-85c3-12515546a681&cursor_ref=pr_footer&cursor_cta=open_in_cursor"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-cursor-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-cursor-light.png"><img alt="Open in Cursor" width="131" height="28" src="https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a> </div> --------- Co-authored-by: Cursor Agent <cursoragent@cursor.com> Co-authored-by: hraness <0thernet@users.noreply.github.com>
![https://cursor.com/assets/images/open-in-web-dark.png"><source](https://cursor.com/assets/images/open-in-web-dark.png"><source){kind=link}
![https://cursor.com/assets/images/open-in-web-light.png"><img](https://cursor.com/assets/images/open-in-web-light.png"><img){kind=link}
![https://cursor.com/assets/images/open-in-web-dark.png"></picture></a> <a](https://cursor.com/assets/images/open-in-web-dark.png"></picture></a> <a){kind=link}
![https://cursor.com/assets/images/open-in-cursor-dark.png"><source](https://cursor.com/assets/images/open-in-cursor-dark.png"><source){kind=link}
![https://cursor.com/assets/images/open-in-cursor-light.png"><img](https://cursor.com/assets/images/open-in-cursor-light.png"><img){kind=link}
![https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a> </div](https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a> </div){kind=link}
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rebasing might not happen immediately, so don't worry if this takes some time.
Note: if you make any changes to this PR yourself, they will take precedence over the rebase.
Bumps vitest from 4.1.11 to 5.0.4.
Release notes
Sourced from vitest's releases.
... (truncated)
Commits
6a11cf6chore: release v5.0.4 (#11554)58c86edchore(deps): update all non-major dependencies (#11550)0fa80f5fix(coverage): filenames containing brackets incorrectly showing as uncovered...bf04b9cfix(browser): run browser instances as workers (#11525)3e3624crefactor: resolve maxWorkers once in config (#11524)26642f7fix: respect root in projects (#11521)c06012afeat(experimental): add an option to cache dependencies instead of statically...4ef000afix(coverage):allowExternalfails to include uncovered files (#11513)1da6640feat: supporttest.ui.themeoption (#11499)b618afdfix(vm): bindthistomodule.exports(#11504)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)