chore(deps-dev): bump the testing group across 1 directory with 2 updates#249
chore(deps-dev): bump the testing group across 1 directory with 2 updates#249dependabot[bot] wants to merge 1 commit into
Conversation
…ates Bumps the testing group with 1 update in the / directory: [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8). Updates `@vitest/coverage-v8` from 4.1.5 to 4.1.6 - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v4.1.6/packages/coverage-v8) Updates `vitest` from 4.1.4 to 4.1.5 - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v4.1.5/packages/vitest) --- updated-dependencies: - dependency-name: "@vitest/coverage-v8" dependency-version: 4.1.6 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: testing - dependency-name: vitest dependency-version: 4.1.5 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: testing ... Signed-off-by: dependabot[bot] <support@github.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 914019a470
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| "@types/react": "^19.2.14", | ||
| "@types/react-dom": "^19.2.3", | ||
| "@vitest/coverage-v8": "4.1.5", | ||
| "@vitest/coverage-v8": "4.1.6", |
There was a problem hiding this comment.
Update Bun lockfile with the dependency bump
Because this repo installs the root workspace with bun install --frozen-lockfile in CI (.github/workflows/ci.yml:47), changing package.json without updating bun.lock leaves the install graph inconsistent: package.json now asks for @vitest/coverage-v8 4.1.6 while bun.lock still pins the root spec and package entry to 4.1.5. In contexts that miss the node_modules cache or build the Docker image, the frozen Bun install will fail or not use the intended bumped dependency, so the Bun lockfile needs to be regenerated alongside this change.
Useful? React with 👍 / 👎.
|
Dependabot can't access a private package registry without explicit configuration. Because of this, Dependabot cannot update this pull request. |
Bumps the testing group with 1 update in the / directory: @vitest/coverage-v8.
Updates
@vitest/coverage-v8from 4.1.5 to 4.1.6Release notes
Sourced from @vitest/coverage-v8's releases.
Commits
a8fd24cchore: release v4.1.6Updates
vitestfrom 4.1.4 to 4.1.5Release notes
Sourced from vitest's releases.
Commits
e399846chore: release v4.1.57dc6d54Revert "fix: respect diff config options in soft assertions (#8696)"9787dedfix: respect diff config options in soft assertions (#8696)325463afix(ast-collect): recognize _vi_import prefix in static test discovery (#10...0e0ff41feat(coverage): istanbul to supportinstrumenteroption (#10119)663b99ffix: aliasagentreporter tominimal(#10157)122c25bfix: fixvi.defineHelpercalled as object method (#10163)6abd557feat(api): make test-specification options writable (#10154)596f739fix: project color label on html reporter (#10142)9423dc0fix: --project negation excludes browser instances (#10131)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 <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions