Skip to content

chore(deps-dev): bump vitest from 4.1.11 to 5.0.0 in the vitest group across 1 directory - #103

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/vitest-4b52c90628
Closed

chore(deps-dev): bump vitest from 4.1.11 to 5.0.0 in the vitest group across 1 directory#103
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/vitest-4b52c90628

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 7, 2026

Copy link
Copy Markdown
Contributor

Bumps the vitest group with 1 update in the / directory: vitest.

Updates vitest from 4.1.11 to 5.0.0

Release notes

Sourced from vitest's releases.

v5.0.0

Vitest 5 is officially out! This release focuses on performance and brings a lot of new features while fixing long-standing bugs. See our blog post for the official announcement.

   🚨 Breaking Changes

... (truncated)

Commits
  • f441c6f chore: release v5.0.0 (#11130)
  • d46a747 fix: treat test.describe as a suite during static collection (#11128)
  • 584cf30 fix: add a warning if inline project has duplicate plugins due to unexpected ...
  • f08ce4b fix: apply queued mocks from doMock() in queue order (fixes #10706) (#11127)
  • 897f51f chore: release v5.0.0-rc.4 (#11107)
  • 1339b06 chore(deps): update all non-major dependencies (#11104)
  • 51e9494 feat!: parse files statically in vitest list by default (#11088)
  • 2122ffd fix: propagate --maxWorkers to projects (#11102)
  • dc10f5f fix(browser): report the action error when a task times out (#11101)
  • d4fe198 feat: promote clearCache out of experimental (#11086)
  • Additional commits viewable in compare view

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Sep 7, 2026
@TheCryptoDonkey

Copy link
Copy Markdown
Member

@dependabot recreate

Bumps the vitest group with 1 update in the / directory: [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest).


Updates `vitest` from 4.1.11 to 5.0.0
- [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.0/packages/vitest)

---
updated-dependencies:
- dependency-name: vitest
  dependency-version: 5.0.0
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: vitest
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot changed the title chore(deps-dev): bump vitest from 4.1.11 to 5.0.0 in the vitest group chore(deps-dev): bump vitest from 4.1.11 to 5.0.0 in the vitest group across 1 directory Sep 8, 2026
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/vitest-4b52c90628 branch from 00edc02 to a0fdb06 Compare September 8, 2026 16:40
TheCryptoDonkey added a commit that referenced this pull request Sep 8, 2026
)

Supersedes #103, which could not install.

The group config here was already correct, patterns ["vitest", "@vitest/*"]
across all update types. Dependabot still bumped vitest's range in package.json
to ^5.0.0 while moving @vitest/coverage-v8 only in the lockfile, leaving its
declared range at ^4.1.1. npm ci therefore resolved coverage-v8 to 4.1.11,
which peer-pins the exact vitest it no longer had:

  While resolving: @vitest/coverage-v8@4.1.11
  Found: vitest@5.0.0
  peer vitest@"4.1.11" from @vitest/coverage-v8@4.1.11

Recreating the PR reproduced the identical split, so the manifest bump is done
by hand here rather than retried a third time.

Both ranges to ^5.0.0, lockfile regenerated. npm ci clean, 1669 tests pass
across 105 files on vitest 5.
@TheCryptoDonkey

Copy link
Copy Markdown
Member

Superseded by #104, which bumps both packages' declared ranges together.

This PR could not install. The group config is correct, but dependabot moved vitest to ^5.0.0 in package.json while updating @vitest/coverage-v8 only in the lockfile, leaving its range at ^4.1.1. npm ci then resolved coverage-v8 to 4.1.11, which peer-pins the exact vitest it no longer had. Asking for a recreate reproduced the identical split, so #104 does the manifest bump directly. 1669 tests pass on vitest 5.

@dependabot @github

dependabot Bot commented on behalf of github Sep 8, 2026

Copy link
Copy Markdown
Contributor Author

This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests.

To ignore these dependencies, configure ignore rules in dependabot.yml

@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/vitest-4b52c90628 branch September 8, 2026 18:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant