Repository navigation
chore(deps-dev): bump the vitest group across 1 directory with 3 updates - #45
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
dependabot
Bot
added
dependencies
dependabot
Bot
added
dependencies
htcom-code
added a commit
that referenced
this pull request
Oct 6, 2026
Dependabot opened three patch updates: #45 (vitest group 5.0.1 to 5.0.2), #46 (vite 8.3.0 to 8.3.1, demo) and #47 (`@microsoft/api- extractor` 7.59.2 to 7.59.3, the dev group). All three rewrite `pnpm-lock.yaml`, and #45 and #46 conflict directly because vitest's snapshot keys carry vite's version as a peer suffix, so they land as one branch. The lockfile is the union of what the three pull requests resolved. A fresh resolve would have pulled vite 8.3.2 and rolldown 1.2.12, which no pull request carried; the conflict was resolved by keeping the vitest side with its vite peer suffix moved to 8.3.1. The package set matches main plus each pull request's additions and removals exactly, and `pnpm install --frozen-lockfile` accepts it. Nothing here reaches a published package: every change is in devDependencies, and `pnpm api` reports all five API reports unchanged. Tags: #deps
Bumps the vitest group with 3 updates in the / directory: [@vitest/browser](https://github.com/vitest-dev/vitest/tree/HEAD/packages/browser), [@vitest/browser-playwright](https://github.com/vitest-dev/vitest/tree/HEAD/packages/browser-playwright) and [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest). Updates `@vitest/browser` from 5.0.2 to 5.0.3 - [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.3/packages/browser) Updates `@vitest/browser-playwright` from 5.0.2 to 5.0.3 - [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.3/packages/browser-playwright) Updates `vitest` from 5.0.2 to 5.0.3 - [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.3/packages/vitest) --- updated-dependencies: - dependency-name: "@vitest/browser" dependency-version: 5.0.2 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: vitest - dependency-name: "@vitest/browser-playwright" dependency-version: 5.0.2 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: vitest - dependency-name: vitest dependency-version: 5.0.2 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: vitest ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
changed the title
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/vitest-1d50a822d5
branch
from
October 6, 2026 02:36
15fd285 to
ea9c645
Compare
htcom-code
added a commit
that referenced
this pull request
Oct 6, 2026
Dependabot opened three patch updates: #45 (vitest group 5.0.2 to 5.0.3), #46 (vite 8.3.1 to 8.3.2, demo) and #49 (`@types/node` 26.6.3 to 26.6.4, the dev group). vitest's snapshot keys carry both vite's and `@types/node`'s versions as peer suffixes, so each pull request rewrites the same lockfile lines and they land as one branch. The lockfile is the union of what the three pull requests resolved. Re-resolving the peer suffixes left four transitive packages behind (`rolldown`, `@oxc-project/types`, `chai`, `tinyrainbow`); a targeted update moved them to the pull requests' versions. #46 moves only postcss's `source-map-js` edge to 1.2.2, which `pnpm update` cannot express, so that entry was copied from its lockfile. The package set matches main plus each pull request's changes exactly. `why-is-node-running` steps back to 3.2.1 because vitest 5.0.3 pins it exactly. Nothing here reaches a published package: every change is in devDependencies and `pnpm api` reports all five API reports unchanged. Tags: #deps
Contributor
Author
|
Looks like these dependencies are no longer updatable, so this is no longer needed. |
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.
Bumps the vitest group with 3 updates in the / directory: @vitest/browser, @vitest/browser-playwright and vitest.
Updates
@vitest/browserfrom 5.0.2 to 5.0.3Release notes
Sourced from @vitest/browser's releases.
Commits
33cadeachore: release v5.0.3 (#11409)062c75dchore: fix standalone docs build, update exports maps (#11394)c22aba9fix(browser):toMatchScreenshotuses wrong reference on retried tests (#11393)15cc006fix: don't print an interceptor warning in browser mode (#11377)a029e76chore: migrate to oxc (#11367)Updates
@vitest/browser-playwrightfrom 5.0.2 to 5.0.3Release notes
Sourced from @vitest/browser-playwright's releases.
Commits
33cadeachore: release v5.0.3 (#11409)062c75dchore: fix standalone docs build, update exports maps (#11394)7c36748fix(browser): ignore page crash while cancelling (#11386)a029e76chore: migrate to oxc (#11367)Updates
vitestfrom 5.0.2 to 5.0.3Release notes
Sourced from vitest's releases.
Commits
33cadeachore: release v5.0.3 (#11409)346d389fix(vm): don't reuse scripts across vite environments (#11395)f6c9a49fix(deps): pinwhy-is-node-runningto3.2.1to avoid users running into `...062c75dchore: fix standalone docs build, update exports maps (#11394)caf2887fix(vm): do not optimize deps from index.html (fix #11329) (#11360)50312ebfix(pool): preserve unique pool ids whengroupOrderis set (#11392)7c36748fix(browser): ignore page crash while cancelling (#11386)92ba7fcfix: scope cache key generators to projects (fix #11281) (#11301)38f9885fix(cache): revalidate imports of cached modules (#11381)b24585ffix: don't retry whentest.failsexpectedly failed (#11219)