Repository navigation
chore: bump @vitest/mocker and vitest - #1064
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
auto-merge
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/multi-fea79c7e0d
branch
4 times, most recently
from
November 1, 2026 16:08
a99ba0f to
3fb9184
Compare
ovflowd
added a commit
that referenced
this pull request
Nov 1, 2026
@cloudflare/vitest-pool-workers is deprecated: it was renamed to @cloudflare/vitest-plugin at 1.0.0 and its last release (0.23.0) peers on vitest ^4.1.0, so the vitest 5 bump in #1042 and the security update in #1064 both fail `npm ci` with ERESOLVE. The plugin peers on vitest ^4.1.0 || ^5.0.0. Migration, per the upstream changelog: - vitest.config.ts uses `defineConfig` with the `cloudflareTest()` plugin instead of `defineWorkersConfig` + `poolOptions.workers`. - `fetchMock` is gone from `cloudflare:test`, so the S3 and misc tests spy on `globalThis.fetch`, reject anything unmocked and assert the expected calls instead of `assertNoPendingInterceptors()`. - `ProvidedEnv` is replaced by `Cloudflare.Env`, and `env` comes from `cloudflare:workers`. - `vi.mock` calls move to module top level, which vitest 5 requires. This also clears the open vitest and @vitest/mocker advisories. The plugin pins wrangler 4.156.0 exactly, so the lockfile resolves root wrangler to it as well (within the existing ^4.130.0 range). Assisted-by: Claude Opus 5.5 <noreply@anthropic.com>
Removes [@vitest/mocker](https://github.com/vitest-dev/vitest/tree/HEAD/packages/mocker). It's no longer used after updating ancestor dependency [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest). These dependencies need to be updated together. Removes `@vitest/mocker` Updates `vitest` from 3.2.4 to 5.0.5 - [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.5/packages/vitest) --- updated-dependencies: - dependency-name: "@vitest/mocker" dependency-version: dependency-type: indirect - dependency-name: vitest dependency-version: 5.0.5 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/multi-fea79c7e0d
branch
from
November 1, 2026 17:13
3fb9184 to
6b5e259
Compare
ovflowd
added a commit
that referenced
this pull request
Nov 1, 2026
@cloudflare/vitest-pool-workers is deprecated: it was renamed to @cloudflare/vitest-plugin at 1.0.0 and its last release (0.23.0) peers on vitest ^4.1.0, so the vitest 5 bump in #1042 and the security update in #1064 both fail `npm ci` with ERESOLVE. The plugin peers on vitest ^4.1.0 || ^5.0.0. Migration, per the upstream changelog: - vitest.config.ts uses `defineConfig` with the `cloudflareTest()` plugin instead of `defineWorkersConfig` + `poolOptions.workers`. - `fetchMock` is gone from `cloudflare:test`, so the S3 and misc tests spy on `globalThis.fetch`, reject anything unmocked and assert the expected calls instead of `assertNoPendingInterceptors()`. - `ProvidedEnv` is replaced by `Cloudflare.Env`, and `env` comes from `cloudflare:workers`. - `vi.mock` calls move to module top level, which vitest 5 requires. This also clears the open vitest and @vitest/mocker advisories. The plugin pins wrangler 4.156.0 exactly, so the lockfile resolves root wrangler to it as well (within the existing ^4.130.0 range). Assisted-by: Claude Opus 5.5 <noreply@anthropic.com>
ovflowd
added a commit
that referenced
this pull request
Nov 1, 2026
chore: migrate to @cloudflare/vitest-plugin and vitest 5 @cloudflare/vitest-pool-workers is deprecated: it was renamed to @cloudflare/vitest-plugin at 1.0.0 and its last release (0.23.0) peers on vitest ^4.1.0, so the vitest 5 bump in #1042 and the security update in #1064 both fail `npm ci` with ERESOLVE. The plugin peers on vitest ^4.1.0 || ^5.0.0. Migration, per the upstream changelog: - vitest.config.ts uses `defineConfig` with the `cloudflareTest()` plugin instead of `defineWorkersConfig` + `poolOptions.workers`. - `fetchMock` is gone from `cloudflare:test`, so the S3 and misc tests spy on `globalThis.fetch`, reject anything unmocked and assert the expected calls instead of `assertNoPendingInterceptors()`. - `ProvidedEnv` is replaced by `Cloudflare.Env`, and `env` comes from `cloudflare:workers`. - `vi.mock` calls move to module top level, which vitest 5 requires. This also clears the open vitest and @vitest/mocker advisories. The plugin pins wrangler 4.156.0 exactly, so the lockfile resolves root wrangler to it as well (within the existing ^4.130.0 range). Assisted-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: Claudio Wunder <cwunder@gnome.org>
Contributor
Author
|
Looks like these dependencies are up-to-date now, 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.
Removes @vitest/mocker. It's no longer used after updating ancestor dependency vitest. These dependencies need to be updated together.
Removes
@vitest/mockerUpdates
vitestfrom 3.2.4 to 5.0.5Release notes
Sourced from vitest's releases.
... (truncated)
Commits
7a825dbchore: release v5.0.5 (#11609)6621a72fix: abort all running tests on cancel (#11606)e9c3d72fix: release mocks of finished test files (#11607)8dd67c2fix(browser): run global setup once with instances (#11596)6c5a447fix: run hook cleanups when a later hook fails (#11605)9697b38fix: keep the import frame in native loader errors (#11599)6498b66fix(browser): wait 30s for the browser to close (#11601)f161e6dfix(browser): drop late connections of closed sessions (#11600)fe86a64fix: skip builtin loading in async leak detector (#11598)6ae8e89fix(reporter): end reason'failed'on worker crash (#11568)Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for vitest since your current version.