chore(deps): bump @vitest/mocker from 4.1.9 to 5.0.0 in the npm_and_yarn group across 0 directory - #16
Merged
Conversation
Updates `@vitest/mocker` from 4.1.9 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/mocker) --- updated-dependencies: - dependency-name: "@vitest/mocker" dependency-version: 5.0.0 dependency-type: indirect dependency-group: npm_and_yarn ... Signed-off-by: dependabot[bot] <support@github.com>
BenKalsky
deleted the
dependabot/npm_and_yarn/npm_and_yarn-8bd3e5320a
branch
September 12, 2026 18:43
BenKalsky
added a commit
that referenced
this pull request
Sep 12, 2026
Lockfile only; package.json is untouched and every change resolves inside ranges already declared. The Vitest 5 bump (#16) left four advisories in `pnpm audit`, all dev-only via vitest -> vite -> postcss: postcss 8.5.16 -> 8.5.28 (1 high, 1 moderate: sourceMappingURL path traversal / arbitrary .map read) nanoid 3.3.15 -> 3.3.19 (2 high: generators can loop indefinitely) The refresh also carries routine patch/minor updates to the dev toolchain (happy-dom 20.14.5, rolldown 1.1.5, lightningcss 1.33.0, ws 8.21.3) and to devDependencies used only by the tests (react and react-dom 19.3.0, @testing-library/react 16.3.3, sumit-api 0.4.1). None of these reach the published package, whose peer ranges are unchanged. Verified: `pnpm audit` reports no known vulnerabilities; typecheck, build and all 33 tests pass. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
BenKalsky
added a commit
that referenced
this pull request
Sep 12, 2026
Vitest 5 (#16) requires Node ^22.12.0 || ^24 || >=26 and declares a peer of @types/node ^22 || >=24, but the repo still said Node 20: - `@types/node` ^20.19.35 -> ^22.19.0 (resolves 22.20.2). Every install printed an unmet-peer warning; it is gone. - `.nvmrc` pins 22.12.0, the real floor rather than a bare `22`, which would let 22.0-22.11 through and fail the suite unexplained. - CLAUDE.md states the requirement next to the dev commands. Toolchain only: the package declares no `engines` field and its peer ranges are unchanged, so consumers of the published library see no difference. CI already runs Node 22 (latest 22.x, past 22.12). Verified: no peer warnings on install; typecheck, build and all 33 tests pass; `pnpm audit` clean. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
Updates
@vitest/mockerfrom 4.1.9 to 5.0.0Release notes
Sourced from @vitest/mocker's releases.
... (truncated)
Commits
f441c6fchore: release v5.0.0 (#11130)897f51fchore: release v5.0.0-rc.4 (#11107)7db80dcchore: release v5.0.0-rc.3 (#11089)732df2cfix(deps): update all non-major dependencies (#11043)1e9f80eperf(vm): don't prewarm modules the worker never requests (#11033)af83d1bchore: release v5.0.0-rc.2 (#10976)8ff9b9afix(mocker): restrict redirect mocks to the fs allowlist (#10972)65263d7fix(deps): update all non-major dependencies (#10966)a7fa111chore: release v5.0.0-rc.1 (#10920)0553851chore: add Knip checks (#10847)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 conditionsYou can disable automated security fix PRs for this repo from the Security Alerts page.