Skip to content

deps: bump the worker-test-toolchain group across 1 directory with 4 updates - #342

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/worker-test-toolchain-5e6f806296
Closed

deps: bump the worker-test-toolchain group across 1 directory with 4 updates#342
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/worker-test-toolchain-5e6f806296

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 20, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Bumps the worker-test-toolchain group with 4 updates in the / directory: @cloudflare/workers-types, @vitest/coverage-istanbul, vitest and wrangler.

Updates @cloudflare/workers-types from 5.20261012.1 to 5.20261016.1

Commits

Updates @vitest/coverage-istanbul from 4.1.11 to 5.0.5

Release notes

Sourced from @​vitest/coverage-istanbul's releases.

v5.0.5

   🐞 Bug Fixes

    View changes on GitHub

v5.0.4

   🚀 Features

   🐞 Bug Fixes

... (truncated)

Commits

Updates vitest from 4.1.11 to 5.0.5

Release notes

Sourced from vitest's releases.

v5.0.5

   🐞 Bug Fixes

    View changes on GitHub

v5.0.4

   🚀 Features

   🐞 Bug Fixes

... (truncated)

Commits

Updates wrangler from 4.149.0 to 4.151.1

Release notes

Sourced from wrangler's releases.

wrangler@4.151.1

Patch Changes

  • #15541 e13d5cc Thanks @​mack-erel! - Keep remote dev sessions alive through transient network failures

    wrangler dev --remote and getPlatformProxy() refresh their preview token before it expires, but a single failed refresh — for example while the network was briefly down — stopped refreshing for good, leaving the session broken until restart. A failed refresh now retries every minute until it succeeds. Rebuilds also no longer push the refresh past the session's expiry.

  • #16284 42c6912 Thanks @​karloper! - Fix wrangler rollback reporting success after the changed secrets confirmation is declined

    Previously, declining the "The following secrets have changed…" confirmation printed "Aborting rollback..." and then also printed a success message and the target version as the "Current Version ID", even though no deployment was made and the original version was still live. Wrangler now stops after aborting, so the output matches what is actually deployed.

  • #13742 4a5377f Thanks @​edmundhung! - Hide the wrangler dev hotkey bar when Turborepo does not forward input

  • Updated dependencies [e1d1b77]:

wrangler@4.151.0

Minor Changes

  • #16245 d6b1c82 Thanks @​WalshyDev! - Include source maps by default in wrangler build --experimental-cf-build-output

    Build Output now matches wrangler deploy and wrangler versions upload, which upload source maps by default, so Workers built for tools like cf get stack traces that point at the original source. Source maps that can't be resolved are skipped rather than failing the build. Set upload_source_maps = false to opt out.

Patch Changes

  • #16220 97b2fb1 Thanks @​FlorentCollin! - Support local D1 queries through the experimental d1_binding_jsrpc compatibility flag

    Local D1 bindings now implement the RPC query backend used by D1Database.query() and prepared-statement methods when the flag is enabled. Queries reuse local SQLite execution, including transactional batches, execution metadata, and session bookmarks, while bindings without the flag continue to use HTTP. Update the bundled workerd runtime to 1.20261012.1 and align the default compatibility date with that release.

  • Updated dependencies [f360829, 97b2fb1, 97b2fb1, acd2822]:

wrangler@4.150.0

Minor Changes

  • #16231 091e5ec Thanks @​WalshyDev! - Upload source maps by default for wrangler deploy, wrangler versions upload and wrangler preview

    When upload_source_maps isn't set in config or via --upload-source-maps, Wrangler now generates and uploads source maps so stack traces in logs and wrangler tail point at your original source without extra setup. In this default mode, source maps that can't be resolved (for example inline data: maps or missing .map files from a custom build) are skipped rather than failing the upload. Setting upload_source_maps = true keeps the existing strict behaviour, and upload_source_maps = false (or --no-upload-source-maps for deploy and versions upload) opts out.

    wrangler build --experimental-cf-build-output is unchanged and still only includes source maps when upload_source_maps = true.

  • #16128 daae435 Thanks @​redsteadz! - Stop wrangler deploy, wrangler versions upload and wrangler preview in projects that build for the Cloudflare CLI (cf)

    If your project builds through cf, deploying it with Wrangler reads a different configuration, so it could update the wrong Worker or fail without explaining why. These commands now stop before uploading anything, name the .cloudflare/output directory they found, and tell you to run cf deploy instead. If that directory is just left over from an earlier build, deleting it restores the Wrangler workflow.

    Ordinary Wrangler projects are unaffected, and --dry-run still works on deploy and versions upload. This is a new guard for the experimental Build Output Specification rather than a fix, and it gives three stable commands a failure mode they did not have before, so it is a minor.

Patch Changes

... (truncated)

Commits
  • e7f9e4e Version Packages (#16287)
  • 4a5377f [wrangler] Hide unusable dev hotkeys under Turborepo (#13742)
  • 42c6912 [wrangler] Don't report rollback success after declining changed secrets conf...
  • e13d5cc [remote-bindings] Retry proactive preview token refresh after a transient fai...
  • b81efbc Version Packages (#16241)
  • d6b1c82 Generate source maps by default for Vite plugin Workers and Build Output (#16...
  • fb3d9c8 Version Packages (#16162)
  • 091e5ec [wrangler] Upload source maps by default (#16231)
  • ea64ec4 [wrangler] Preserve D1 migration paths during redirected provisioning (#15517)
  • d232454 [wrangler] Preserve public HTTPS response URLs behind TLS-terminating proxies...
  • Additional commits viewable in compare view

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Oct 20, 2026
@dependabot
deps: bump the worker-test-toolchain group across 1 directory with 4 …
a31ab46 
…updates

Bumps the worker-test-toolchain group with 4 updates in the / directory: [@cloudflare/workers-types](https://github.com/cloudflare/workerd), [@vitest/coverage-istanbul](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-istanbul), [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) and [wrangler](https://github.com/cloudflare/workers-sdk/tree/HEAD/packages/wrangler).


Updates `@cloudflare/workers-types` from 5.20261012.1 to 5.20261016.1
- [Release notes](https://github.com/cloudflare/workerd/releases)
- [Changelog](https://github.com/cloudflare/workerd/blob/main/RELEASE.md)
- [Commits](https://github.com/cloudflare/workerd/commits)

Updates `@vitest/coverage-istanbul` from 4.1.11 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/coverage-istanbul)

Updates `vitest` from 4.1.11 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)

Updates `wrangler` from 4.149.0 to 4.151.1
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.151.1/packages/wrangler)

---
updated-dependencies:
- dependency-name: "@cloudflare/workers-types"
  dependency-version: 5.20261016.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: worker-test-toolchain
- dependency-name: "@vitest/coverage-istanbul"
  dependency-version: 5.0.5
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: worker-test-toolchain
- dependency-name: vitest
  dependency-version: 5.0.5
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: worker-test-toolchain
- dependency-name: wrangler
  dependency-version: 4.151.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: worker-test-toolchain
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot changed the title deps: bump the worker-test-toolchain group with 4 updates deps: bump the worker-test-toolchain group across 1 directory with 4 updates Oct 20, 2026
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/worker-test-toolchain-5e6f806296 branch from 18ca678 to a31ab46 Compare October 20, 2026 11:54
@skyphusion-rollins Rollins (skyphusion-rollins) mentioned this pull request Oct 20, 2026
Open
@skyphusion-mackaye

skyphusion-mackaye commented Oct 20, 2026

Copy link
Copy Markdown
Member

Dropping this unmerged. It cannot be made green by anything in this repository.

This is not a test failure. npm ci crashes before any test runs:

Cannot read properties of null (reading 'edgesOut')

The group takes vitest 4.1.11 -> 5.0.5 while leaving @cloudflare/vitest-pool-workers at
^0.23.0, which peer-requires vitest ^4.1.0. Isolated probe with nothing else installed:

peer vitest@"^4.1.0" from @cloudflare/vitest-pool-workers@0.23.0   -> ERESOLVE

The discriminator: a control with vitest ^4.1.11 exits 0 across 84 packages, and npm ci
against main's lockfile in the same clone also exits 0. So the probe distinguishes, and the
crash belongs to this pull request's lockfile rather than to the repo.

0.23.0 is the latest release of that package AND it is deprecated: it was renamed to
@cloudflare/vitest-plugin, and @cloudflare/vitest-plugin@1.4.5 peers
^4.1.0 || ^5.0.0. So the route to vitest 5 is a package migration, not a version bump, and
no amount of rebasing this will reach it.

The migration is tracked in common-thread#344.

One consequence worth stating since it is the predictable annoyance: dependabot will re-propose
this bump until that migration lands. If the churn becomes noise before then, a temporary
ignore for vitest >= 5 belongs in .github/dependabot.yml, removed as part of #344 rather
than left behind.

Measured by rollins-viv1020.

@dependabot @github

dependabot Bot commented on behalf of github Oct 20, 2026

Copy link
Copy Markdown
Contributor Author

This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests.

To ignore these dependencies, configure ignore rules in dependabot.yml

@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/worker-test-toolchain-5e6f806296 branch October 20, 2026 12:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@skyphusion-mackaye