Bump the workerd-and-workers-types group across 1 directory with 2 updates by dependabot[bot] · Pull Request #15123 · cloudflare/workers-sdk

dependabot · 2026-08-11T06:06:42Z

Bumps the workerd-and-workers-types group: workerd 1.20260804.1 → 1.20260811.1 and @cloudflare/workers-types 4.20260702.1 → 5.20260811.1.

(The dependabot details below quote 1.20260808.1/5.20260808.1. The types entry is a caret range, so it had already resolved to 5.20260811.1 in the lockfile while workerd stayed pinned to 1.20260808.1; the two are released in lockstep, so both are now on 1.20260811.1/5.20260811.1. The nodejs_compat enable dates are unchanged in that release.)

This bump is not self-contained, so it carries the changes needed to make the repo work against the new runtime.

`nodejs_compat` is now on by default

workerd now marks both nodejs_compat and nodejs_compat_v2 as enabled by default from compatibility date 2026-08-04 onwards, and rejects a config that specifies a flag its compatibility date already enables:

The compatibility flag nodejs_compat_v2 became the default as of 2026-08-04 so does not need to be specified anymore.

getNodeCompat() in Miniflare only ever treated Node.js compatibility as enabled when a flag was listed explicitly, so for those dates it reported that there was no Node.js compatibility at all. Consequences:

@cloudflare/vitest-pool-workers added a redundant nodejs_compat_v2 to its runner worker, which workerd then rejected. This is the visible failure — it defaults the compatibility date to today's date, so it broke as soon as the runtime was bumped, without anyone changing a config.
Wrangler would have skipped its unenv polyfills, and the Vite plugin would have substituted process.env with an empty object.

getNodeCompat() now resolves both flags the way workerd does, and honours no_nodejs_compat, which it previously ignored entirely. The date lives in one place, as NODEJS_COMPAT_DEFAULT_ON_DATE in @cloudflare/workers-utils.

There were no tests for getNodeCompat() before; there are now 17 covering the flag/date matrix.

Generated and existing configs

For the same reason, create-cloudflare and wrangler setup no longer add nodejs_compat next to a compatibility date that already enables it — otherwise every newly scaffolded project fails to start. Six C3 templates and the repo's own configs that paired the flag with such a date are updated too.

Two follow-ups in C3, both found by Devin on this PR: it removes the flag when a template or a framework's own scaffolder already wrote it next to such a date, and it no longer relies on that flag to decide whether a project needs @types/node (which would otherwise have quietly cost every new TypeScript project its Node.js typings). The flag resolution now lives in @cloudflare/workers-utils as resolveNodejsCompat(), shared with Miniflare instead of duplicated.

Tooling deliberately does not strip a redundant flag from user config. The compatibility date is the opt-in, so workerd's error is the correct signal, and the changeset documents the one-line fix. Worth noting the blast radius is wider than local dev: the control plane runs the same validation, so an existing Worker with nodejs_compat will be rejected by wrangler deploy the first time it bumps its compatibility date past 2026-08-04.

Known issues, tracked separately

Devin raised three findings against the other commits already on this branch. They are split out so this bump is not held up by them:

[vitest-pool-workers] inject() in pool options no longer infers types or checks keys #15137 — inject() in vitest-pool-workers pool options no longer infers types or checks keys
[workflows] Local deleteBatch() always reports success, so failures are invisible #15138 — local deleteBatch() always reports success, so failures are invisible
[workflows] Local delete() and deleteBatch() have no test coverage #15139 — local delete()/deleteBatch() have no test coverage

Nuxt e2e tests quarantined

Nitro's Cloudflare preset unconditionally adds nodejs_compat to the wrangler config it generates, and points wrangler at it through a .wrangler/deploy/config.json redirect, so it overrides the user's own config:

Using redirected Wrangler configuration.
 - Configuration being used: "dist/_worker.js/wrangler.json"
 - Original user's configuration: "wrangler.jsonc"

Against this runtime workerd refuses to start, and the Nuxt framework e2e tests fail as a fetch failed timeout against a dev server that never booted. C3's own templates are clean, so this is not fixable from our side of the config — and by the same control-plane validation noted above, wrangler deploy of a Nuxt app is affected too, not just local dev.

The six nuxt:* e2e configs are quarantined so this bump is not held up. Tracked in #15146, filed upstream as nitrojs/nitro#4527.

Sanitising redundant flags in wrangler/miniflare before handing them to workerd would fix this for everyone affected, but that reverses the decision described above and is deliberately left out of this PR; the trade-offs are recorded in #15146.

`@cloudflare/workers-types` v5

The types major adds the Node.js compatibility globals it did not cover before, including process. Like every other ambient global it declares, process is a const, so TypeScript no longer treats it as a property of typeof globalThis, and globalThis.process = process in the pages-nodejs-v2-compat fixture stopped type checking. That assignment is there to check the assignment does not produce a build time error, so it is kept as-is and the type error is silenced, preserving the bundler coverage.

Tests
- Tests included/updated
- Automated tests not possible - manual testing has been completed as follows:
- Additional testing not necessary because:
Public documentation
- Cloudflare docs PR(s):
- Documentation not necessary because: the behaviour change is workerd's, not this repo's — this PR only aligns the tooling with it. Any docs that recommend adding nodejs_compat are stale as a result of the runtime change and are owned by it.

Original dependabot description

Bumps the workerd-and-workers-types group with 2 updates in the / directory: @cloudflare/workers-types and workerd.

Updates @cloudflare/workers-types from 4.20260702.1 to 5.20260808.1

Commits

See full diff in compare view

Updates workerd from 1.20260804.1 to 1.20260808.1

Release notes

Sourced from workerd's releases.

v1.20260808.1

What's Changed

Make ctx.abort() (for stateless workers) non-experimental. by @kentonv in cloudflare/workerd#6930

Replace raw Writer& with kj::Ptr by @jasnell in cloudflare/workerd#6931

Re-land the fix and regression test for vuln-187 by @harrishancock in cloudflare/workerd#6934

Full Changelog: cloudflare/workerd@v1.20260807.2...v1.20260808.1

v1.20260807.2

What's Changed

2026 08 07 upstream by @mikea in cloudflare/workerd#6929

attempt to fix release by @mikea in cloudflare/workerd#6933

Full Changelog: cloudflare/workerd@v1.20260807.1...v1.20260807.2

v1.20260807.1

What's Changed

2026 08 05 upstream by @mikea in cloudflare/workerd#6916

Full Changelog: cloudflare/workerd@v1.20260806.1...v1.20260807.1

v1.20260806.1

Full Changelog: cloudflare/workerd@v1.20260805.1...v1.20260806.1

v1.20260805.1

What's Changed

2026 07 31 upstream by @mikea in cloudflare/workerd#6909

Full Changelog: cloudflare/workerd@v1.20260804.1...v1.20260805.1

Commits

a955a87 Release 2026-08-08
a861db3 Merge pull request #6934 from cloudflare/harris/2026-08-07-reland-vuln-187
5d701d3 Merge pull request #6931 from cloudflare/jasnell/writer-kj-ptr
a5ce01f Merge pull request #6930 from cloudflare/kenton/enable-ctx-abort
8d45594 attempt to fix release (#6933)
322d59b Make ctx.abort() (for stateless workers) non-experimental.
adb9a5d Do not pass raw reference over Writer attach
c317b59 Use kj::Ptr<Writer> instead of Writer&
e7b2192 Fix issue where IoContext could be aborted while waiting for lock.
5374389 Merge pull request #6929 from cloudflare/maizatskyi/2026-08-07-upstream
Additional commits viewable in compare view

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

changeset-bot · 2026-08-11T06:06:46Z

🦋 Changeset detected

Latest commit: 8219355

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 13 packages

Name	Type
miniflare	Minor
wrangler	Minor
@cloudflare/vitest-pool-workers	Patch
@cloudflare/autoconfig	Patch
create-cloudflare	Patch
@cloudflare/vite-plugin	Minor
@cloudflare/workers-utils	Minor
@cloudflare/deploy-helpers	Patch
@cloudflare/pages-shared	Patch
@cloudflare/remote-bindings	Patch
@cloudflare/runtime-types	Patch
@cloudflare/cli-shared-helpers	Patch
@cloudflare/workers-auth	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

workers-devprod · 2026-08-11T06:07:11Z

Codeowners approval required for this PR:

@cloudflare/workflows
✅ @cloudflare/wrangler

Show detailed file reviewers

packages/workflows-shared/src/binding.ts: [@cloudflare/workflows]

github-actions · 2026-08-11T06:10:58Z

✅ All changesets look good

pkg-pr-new · 2026-08-11T09:21:40Z

@cloudflare/autoconfig

npm i https://pkg.pr.new/@cloudflare/autoconfig@15123

@cloudflare/build-output-utils

npm i https://pkg.pr.new/@cloudflare/build-output-utils@15123

@cloudflare/config

npm i https://pkg.pr.new/@cloudflare/config@15123

create-cloudflare

npm i https://pkg.pr.new/create-cloudflare@15123

@cloudflare/deploy-helpers

npm i https://pkg.pr.new/@cloudflare/deploy-helpers@15123

@cloudflare/kv-asset-handler

npm i https://pkg.pr.new/@cloudflare/kv-asset-handler@15123

miniflare

npm i https://pkg.pr.new/miniflare@15123

@cloudflare/pages-functions

npm i https://pkg.pr.new/@cloudflare/pages-functions@15123

@cloudflare/pages-shared

npm i https://pkg.pr.new/@cloudflare/pages-shared@15123

@cloudflare/unenv-preset

npm i https://pkg.pr.new/@cloudflare/unenv-preset@15123

@cloudflare/vite-plugin

npm i https://pkg.pr.new/@cloudflare/vite-plugin@15123

@cloudflare/vitest-pool-workers

npm i https://pkg.pr.new/@cloudflare/vitest-pool-workers@15123

@cloudflare/workers-auth

npm i https://pkg.pr.new/@cloudflare/workers-auth@15123

@cloudflare/workers-editor-shared

npm i https://pkg.pr.new/@cloudflare/workers-editor-shared@15123

@cloudflare/workers-utils

npm i https://pkg.pr.new/@cloudflare/workers-utils@15123

wrangler

npm i https://pkg.pr.new/wrangler@15123

commit: 2372e7a

…dates Bumps the workerd-and-workers-types group with 2 updates in the / directory: [@cloudflare/workers-types](https://github.com/cloudflare/workerd) and [workerd](https://github.com/cloudflare/workerd). Updates `@cloudflare/workers-types` from 4.20260702.1 to 5.20260808.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 `workerd` from 1.20260804.1 to 1.20260808.1 - [Release notes](https://github.com/cloudflare/workerd/releases) - [Changelog](https://github.com/cloudflare/workerd/blob/main/RELEASE.md) - [Commits](cloudflare/workerd@v1.20260804.1...v1.20260808.1) --- updated-dependencies: - dependency-name: "@cloudflare/workers-types" dependency-version: 5.20260808.1 dependency-type: direct:production update-type: version-update:semver-major dependency-group: workerd-and-workers-types - dependency-name: workerd dependency-version: 1.20260808.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: workerd-and-workers-types ... Signed-off-by: dependabot[bot] <support@github.com>

The following dependency versions have been updated: | Dependency | From | To | | ------------------------- | ------------- | ------------- | | @cloudflare/workers-types | ^5.20260804.1 | ^5.20260808.1 | | workerd | 1.20260804.1 | 1.20260808.1 |

…eBatch()` The updated `@cloudflare/workers-types` now requires `delete()` on workflow instances and `deleteBatch()` on the workflow binding. These methods are now implemented in the local workflows simulator so that local dev and tests match the production API.

workerd now enables the `nodejs_compat` and `nodejs_compat_v2` flags by default for compatibility dates of 2026-08-04 or later, and rejects configs that also specify a flag its compatibility date already enables. `getNodeCompat()` only treated Node.js compatibility as enabled when a flag was listed explicitly, so it reported no Node.js compatibility for such dates. That made `@cloudflare/vitest-pool-workers` add a redundant `nodejs_compat_v2` to its runner worker, which workerd then rejected, and would also have skipped Wrangler's unenv polyfills and substituted `process.env` with an empty object in the Vite plugin. It now resolves both flags the way workerd does, and honours `no_nodejs_compat`. For the same reason `create-cloudflare` and `wrangler setup` no longer add `nodejs_compat` alongside the compatibility date they generate, and the repo's own configurations that paired the flag with such a date are updated.

`@cloudflare/workers-types` v5 declares the Node.js compatibility globals it did not cover before, including `process`. Like the other ambient globals it declares, `process` is a `const`, so TypeScript no longer treats it as a property of `typeof globalThis` and the fixture's `globalThis.process = process` fails to type check. That assignment is deliberate: it is there to check that assigning to `globalThis.process` does not produce a *build* time error. Keep it as it is and silence the type error instead, so the bundler coverage is preserved.

The `@cloudflare/workers-types` catalog entry is a caret range, so it had already resolved to 5.20260811.1 in the lockfile while `workerd` stayed pinned to 1.20260808.1. The two are released in lockstep, so line them up. The `nodejs_compat` and `nodejs_compat_v2` enable dates are unchanged in this release, and no other compatibility flag gained a 2026-08 enable date, so the Node.js compatibility work in this PR is unaffected.

…date Two things in C3 still keyed off the presence of the `nodejs_compat` flag, which is no longer written when the compatibility date already enables it: - `maybeInstallNodeTypes()` decided whether to install `@types/node` and add `node` to the project's `tsconfig.json` from the flag alone, so newly scaffolded TypeScript projects silently lost their Node.js typings. - The flag was only ever added, never removed, so one that a template or a framework's own scaffolder had already written survived next to a compatibility date that enables it, which workerd rejects. The flag resolution itself moves to `@cloudflare/workers-utils` as `resolveNodejsCompat()` so that C3 and Miniflare share one implementation rather than each having their own. Reported by Devin on #15123.

…mpat flag `wrangler types` decides whether to suggest installing `@types/node` from the resolved Node.js compatibility mode, which is now also enabled by a recent enough compatibility date. The message still claimed the suggestion was because "you have the `nodejs_compat` flag", which it now prints for Workers that do not set that flag at all.

…compat Nitro's Cloudflare preset unconditionally adds `nodejs_compat` to the wrangler config it generates and points wrangler at it via a `.wrangler/deploy/config.json` redirect. From compatibility date 2026-08-04 that flag is on by default, so workerd rejects it and the dev server never starts, which the framework e2e tests surface as a `fetch failed` timeout. C3's own templates no longer specify the flag, so this can only be fixed upstream in Nitro or by sanitising redundant flags before they reach workerd. Tracked in #15146.

`ensureNodejsCompatIsEnabled()` reconciled the generated config, but `saveWranglerJsonc()` merges that on top of any wrangler.json(c) already in the project. Once the reconciled list was empty the key was absent from the generated object, so the merge no longer overrode a `nodejs_compat` the framework's own scaffolder had written, while the compatibility date was still replaced with today's — the combination workerd rejects. The reconciliation now runs on the merged result, so it is the config that actually gets written that is checked against its own compatibility date.

…ady enables The pool requires v2 for its runner, so it drops a project's `no_nodejs_compat_v2` and adds the flag itself. On a compatibility date from 2026-08-04 the flag is enabled anyway, so adding it back made workerd refuse to start and no tests ran at all. Dropping the opt-out is now enough on those dates; the flag is only added for earlier ones. Covered by a new `misc-nodejs-optout` project, which fails to boot the runtime without the fix.

penalosa

Codeowners Bypass

workers-devprod

Codeowners reviews satisfied

RespectTH123 · 2026-08-12T18:44:09Z

Bumps the workerd-and-workers-types group: workerd 1.20260804.1 → 1.20260811.1 and @cloudflare/workers-types 4.20260702.1 → 5.20260811.1.

(The dependabot details below quote 1.20260808.1/5.20260808.1. The types entry is a caret range, so it had already resolved to 5.20260811.1 in the lockfile while workerd stayed pinned to 1.20260808.1; the two are released in lockstep, so both are now on 1.20260811.1/5.20260811.1. The nodejs_compat enable dates are unchanged in that release.)

This bump is not self-contained, so it carries the changes needed to make the repo work against the new runtime.

nodejs_compat is now on by default

workerd now marks both nodejs_compat and nodejs_compat_v2 as enabled by default from compatibility date 2026-08-04 onwards, and rejects a config that specifies a flag its compatibility date already enables:
The compatibility flag nodejs_compat_v2 became the default as of 2026-08-04 so does not need to be specified anymore.
getNodeCompat() in Miniflare only ever treated Node.js compatibility as enabled when a flag was listed explicitly, so for those dates it reported that there was no Node.js compatibility at all. Consequences:

@cloudflare/vitest-pool-workers added a redundant nodejs_compat_v2 to its runner worker, which workerd then rejected. This is the visible failure — it defaults the compatibility date to today's date, so it broke as soon as the runtime was bumped, without anyone changing a config.

Wrangler would have skipped its unenv polyfills, and the Vite plugin would have substituted process.env with an empty object.

getNodeCompat() now resolves both flags the way workerd does, and honours no_nodejs_compat, which it previously ignored entirely. The date lives in one place, as NODEJS_COMPAT_DEFAULT_ON_DATE in @cloudflare/workers-utils.

There were no tests for getNodeCompat() before; there are now 17 covering the flag/date matrix.

Generated and existing configs

For the same reason, create-cloudflare and wrangler setup no longer add nodejs_compat next to a compatibility date that already enables it — otherwise every newly scaffolded project fails to start. Six C3 templates and the repo's own configs that paired the flag with such a date are updated too.

Two follow-ups in C3, both found by Devin on this PR: it removes the flag when a template or a framework's own scaffolder already wrote it next to such a date, and it no longer relies on that flag to decide whether a project needs @types/node (which would otherwise have quietly cost every new TypeScript project its Node.js typings). The flag resolution now lives in @cloudflare/workers-utils as resolveNodejsCompat(), shared with Miniflare instead of duplicated.

Tooling deliberately does not strip a redundant flag from user config. The compatibility date is the opt-in, so workerd's error is the correct signal, and the changeset documents the one-line fix. Worth noting the blast radius is wider than local dev: the control plane runs the same validation, so an existing Worker with nodejs_compat will be rejected by wrangler deploy the first time it bumps its compatibility date past 2026-08-04.

Known issues, tracked separately

Devin raised three findings against the other commits already on this branch. They are split out so this bump is not held up by them:

[vitest-pool-workers] inject() in pool options no longer infers types or checks keys #15137 — inject() in vitest-pool-workers pool options no longer infers types or checks keys

[workflows] Local deleteBatch() always reports success, so failures are invisible #15138 — local deleteBatch() always reports success, so failures are invisible

[workflows] Local delete() and deleteBatch() have no test coverage #15139 — local delete()/deleteBatch() have no test coverage

Nuxt e2e tests quarantined

Nitro's Cloudflare preset unconditionally adds nodejs_compat to the wrangler config it generates, and points wrangler at it through a .wrangler/deploy/config.json redirect, so it overrides the user's own config:
Using redirected Wrangler configuration.
 - Configuration being used: "dist/_worker.js/wrangler.json"
 - Original user's configuration: "wrangler.jsonc"
Against this runtime workerd refuses to start, and the Nuxt framework e2e tests fail as a fetch failed timeout against a dev server that never booted. C3's own templates are clean, so this is not fixable from our side of the config — and by the same control-plane validation noted above, wrangler deploy of a Nuxt app is affected too, not just local dev.

The six nuxt:* e2e configs are quarantined so this bump is not held up. Tracked in #15146, filed upstream as nitrojs/nitro#4527.

Sanitising redundant flags in wrangler/miniflare before handing them to workerd would fix this for everyone affected, but that reverses the decision described above and is deliberately left out of this PR; the trade-offs are recorded in #15146.

@cloudflare/workers-types v5

The types major adds the Node.js compatibility globals it did not cover before, including process. Like every other ambient global it declares, process is a const, so TypeScript no longer treats it as a property of typeof globalThis, and globalThis.process = process in the pages-nodejs-v2-compat fixture stopped type checking. That assignment is there to check the assignment does not produce a build time error, so it is kept as-is and the type error is silenced, preserving the bundler coverage.

Tests

Tests included/updated

Automated tests not possible - manual testing has been completed as follows:

Additional testing not necessary because:

Public documentation

Cloudflare docs PR(s):

Documentation not necessary because: the behaviour change is workerd's, not this repo's — this PR only aligns the tooling with it. Any docs that recommend adding nodejs_compat are stale as a result of the runtime change and are owned by it.

Original dependabot description

Bumps the workerd-and-workers-types group with 2 updates in the / directory: @cloudflare/workers-types and workerd.

Updates @cloudflare/workers-types from 4.20260702.1 to 5.20260808.1

Commits

See full diff in compare view

Updates workerd from 1.20260804.1 to 1.20260808.1

Release notes

Sourced from workerd's releases.

v1.20260808.1

What's Changed

Make ctx.abort() (for stateless workers) non-experimental. by @kentonv in cloudflare/workerd#6930

Replace raw Writer& with kj::Ptr by @jasnell in cloudflare/workerd#6931

Re-land the fix and regression test for vuln-187 by @harrishancock in cloudflare/workerd#6934

Full Changelog: cloudflare/workerd@v1.20260807.2...v1.20260808.1

v1.20260807.2

What's Changed

2026 08 07 upstream by @mikea in cloudflare/workerd#6929

attempt to fix release by @mikea in cloudflare/workerd#6933

Full Changelog: cloudflare/workerd@v1.20260807.1...v1.20260807.2

v1.20260807.1

What's Changed

2026 08 05 upstream by @mikea in cloudflare/workerd#6916

Full Changelog: cloudflare/workerd@v1.20260806.1...v1.20260807.1

v1.20260806.1

Full Changelog: cloudflare/workerd@v1.20260805.1...v1.20260806.1

v1.20260805.1

What's Changed

2026 07 31 upstream by @mikea in cloudflare/workerd#6909

Full Changelog: cloudflare/workerd@v1.20260804.1...v1.20260805.1

Commits

a955a87 Release 2026-08-08

a861db3 Merge pull request #6934 from cloudflare/harris/2026-08-07-reland-vuln-187

5d701d3 Merge pull request #6931 from cloudflare/jasnell/writer-kj-ptr

a5ce01f Merge pull request #6930 from cloudflare/kenton/enable-ctx-abort

8d45594 attempt to fix release (#6933)

322d59b Make ctx.abort() (for stateless workers) non-experimental.

adb9a5d Do not pass raw reference over Writer attach

c317b59 Use kj::Ptr<Writer> instead of Writer&

e7b2192 Fix issue where IoContext could be aborted while waiting for lock.

5374389 Merge pull request #6929 from cloudflare/maizatskyi/2026-08-07-upstream

Additional commits viewable in compare view

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

dependabot Bot added ci:skip-pr-description-validation Skip validation of the required PR description format dependencies Used by dependabot to mark PRs as updates to dependencies. package:miniflare Relating to Miniflare labels Aug 11, 2026

dependabot Bot requested a review from workers-devprod as a code owner August 11, 2026 06:06

dependabot Bot added package:miniflare Relating to Miniflare dependencies Used by dependabot to mark PRs as updates to dependencies. ci:skip-pr-description-validation Skip validation of the required PR description format labels Aug 11, 2026

workers-devprod added this to workers-sdk Aug 11, 2026

github-project-automation Bot moved this to Untriaged in workers-sdk Aug 11, 2026

workers-devprod requested review from a team and jamesopstad and removed request for a team August 11, 2026 06:07