Skip to content

chore(deps): bump @vitest/mocker from 4.1.9 to 5.0.0 in the npm_and_yarn group across 0 directory - #16

Merged
BenKalsky merged 1 commit into
mainfrom
dependabot/npm_and_yarn/npm_and_yarn-8bd3e5320a
Sep 12, 2026
Merged

chore(deps): bump @vitest/mocker from 4.1.9 to 5.0.0 in the npm_and_yarn group across 0 directory#16
BenKalsky merged 1 commit into
mainfrom
dependabot/npm_and_yarn/npm_and_yarn-8bd3e5320a

Conversation

@dependabot

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

Copy link
Copy Markdown
Contributor

Updates @vitest/mocker from 4.1.9 to 5.0.0

Release notes

Sourced from @​vitest/mocker'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

Dependabot compatibility score

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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will 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 version will 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
    You can disable automated security fix PRs for this repo from the Security Alerts page.

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>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Sep 10, 2026
@BenKalsky
BenKalsky merged commit 03894d5 into main Sep 12, 2026
2 checks passed
@BenKalsky
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>
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