chore(deps): bump @vitest/coverage-v8 from 4.1.11 to 5.0.1 - #4
dependabot[bot] wants to merge 1 commit into
Conversation
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
dependabot
Bot
changed the title
a5c137c to
5de2aad
Compare
|
@dependabot rebase |
Bumps [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8) from 4.1.11 to 5.0.1. - [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.1/packages/coverage-v8) --- updated-dependencies: - dependency-name: "@vitest/coverage-v8" dependency-version: 5.0.0 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
5de2aad to
b08ccc7
Compare
✅ Deploy Preview for hivecommons-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Superseded by #18, which bumps These two are version-locked, so neither could pass on its own. Vitest 5 also stopped re-exporting |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
![hivecommons-hive[bot]](https://avatars.githubusercontent.com/in/3568013?s=60&v=4){kind=small}
There was a problem hiding this comment.
This is superseded by #18, which bumps @vitest/coverage-v8 and vitest to 5.0.1 together.
Verified, not just from the titles: this diff bumps only @vitest/coverage-v8 to 5.0.1 (package.json, package-lock.json), but the new lockfile entry peer-requires "vitest": "5.0.1" (package-lock.json, node_modules/@vitest/coverage-v8 → peerDependencies), while the repo stays on vitest 4.1.11. That is why this PR's "Run unit tests" check fails — it cannot pass alone. #18 makes the same coverage-v8 bump plus the locked vitest bump and the now-required explicit vite devDependency.
Flagging for a maintainer: if you agree, this one could be closed in favour of #18 (note #18 still has one failing Mermaid test to resolve — commented there). I have not closed anything.
— hive: agent=reviewer backend=copilot model=claude-fable-5 copilot=1.0.88
#4) (#18) * chore(deps): bump vitest and @vitest/coverage-v8 to 5.0.1, add explicit vite Supersedes the separate Dependabot PRs #9 and #4, which had to land together: vitest and @vitest/coverage-v8 are version-locked, and merging either alone breaks the test run. Vitest 5 no longer re-exports vite, so vitest.config.ts failed to type check on the bump alone: vitest.config.ts(2,38): error TS2307: Cannot find module 'vite' vitest.config.ts(13,23): error TS7006: Parameter 'code' implicitly has an 'any' type vitest.config.ts(13,29): error TS7006: Parameter 'id' implicitly has an 'any' type The config imports transformWithEsbuild from vite directly, so vite is now an explicit devDependency pinned to the version already resolved in the lockfile (8.1.5). The implicit-any errors cascade from the failed import and resolve with it. Vitest 5 requires Node 22 and Vite 6.4+. CI runs Node 22 (vitest.yml) and the resolved Vite is 8.1.5, so both floors are met. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Signed-off-by: Andrew Anderson <andy@clubanderson.com> * test: make the mermaid initialize assertion independent of import order Vitest 5 changed module evaluation ordering, so the static `import { MermaidComponent }` at the top of the file is no longer guaranteed to have been evaluated when the assertion runs. The side effect under test (`mermaid.initialize`) fires at the top level of @/lib/Mermaid, so import it explicitly inside the test instead of depending on that ordering. 444 of 445 tests already passed on vitest 5; this was the only one relying on the old behaviour. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Signed-off-by: Andrew Anderson <andy@clubanderson.com> --------- Signed-off-by: Andrew Anderson <andy@clubanderson.com> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
1 participant
Bumps @vitest/coverage-v8 from 4.1.11 to 5.0.1.
Release notes
Sourced from @vitest/coverage-v8's releases.
... (truncated)
Commits
03630a5chore: release v5.0.1 (#11275)f441c6fchore: release v5.0.0 (#11130)c4473e4fix(coverage): prevent crash on/@fs/prepended virtual files (#11119)897f51fchore: release v5.0.0-rc.4 (#11107)7db80dcchore: release v5.0.0-rc.3 (#11089)5f6a5e8feat(coverage): switch to@vitest/istanbuljspackages (#11053)c6174a6fix(coverage): v8 to ignore Vite SSR's generated import bindings (#11023)af83d1bchore: release v5.0.0-rc.2 (#10976)a7fa111chore: release v5.0.0-rc.1 (#10920)0553851chore: add Knip checks (#10847)