Repository navigation
Version Packages - #16915
Version Packages#16915
Conversation
There was a problem hiding this comment.
Superseded by the review of
8bd10466.
This review, of 6945eb10
✅ Approved — This is a routine Changesets version bump. The versions and CHANGELOG entries match the consumed changeset, and no issues were found.
The decision is advisory: this review is a comment and never approves, blocks or requests changes on the pull request.
✅ All checks passed
🚀 Release: ✅ LGTM
Risk: Low. The version bumps and CHANGELOG entries match the consumed changeset and the dependency graph.
Reviewed commit: 6945eb10
@cloudflare/autoconfig
@cloudflare/build-output-utils
@cloudflare/codemods
@cloudflare/config
@cloudflare/containers-shared
create-cloudflare
@cloudflare/deploy-helpers
@cloudflare/kv-asset-handler
miniflare
@cloudflare/pages-functions
@cloudflare/pages-shared
@cloudflare/runtime-types
@cloudflare/unenv-preset
@cloudflare/vite-plugin
@cloudflare/vitest-plugin
@cloudflare/workers-auth
@cloudflare/workers-editor-shared
@cloudflare/workers-utils
wrangler
commit: |
6945eb1 to
8bd1046
Compare
There was a problem hiding this comment.
Superseded by the review of
cbac50bb.
This review, of 8bd10466
✅ Approved — This is a routine Changesets version bump. Both consumed changesets (local Artifacts events, container rollout default) appear in the right CHANGELOGs, and the version bumps match the dependency graph. No issues found.
The decision is advisory: this review is a comment and never approves, blocks or requests changes on the pull request.
✅ All checks passed
🚀 Release: ✅ LGTM
Risk: Low.
The pull request consumes both changesets: local-artifacts-event-ingress and containers-rollout-default-max-instances. It bumps 16 packages:
- Minor:
@cloudflare/config,@cloudflare/codemods,wrangler(4.163.0) andminiflare(5.20261113.1-beta). - Patch:
@cloudflare/workers-utilsand the dependent packages.
Wrangler's CHANGELOG now includes the new container rollout patch entry. The @cloudflare/vitest-plugin CHANGELOG now lists 81e56dd among the updated dependencies. The versions and CHANGELOG entries match the release notes in the description.
Reviewed commit: 8bd10466
8bd1046 to
cbac50b
Compare
There was a problem hiding this comment.
Superseded by the review of
b64cf209.
This review, of cbac50bb
✅ Approved — I found no problems. This is a routine Changesets version bump: all three consumed changesets appear in the right CHANGELOGs, and the version bumps match the changeset levels and the dependency graph.
The decision is advisory: this review is a comment and never approves, blocks or requests changes on the pull request.
✅ All checks passed
🚀 Release: ✅ LGTM
Risk: Medium. Behaviour changes in three areas:
- local Artifacts events that start Workflows (#16246)
- running experimental projects with their installed Vite or Vite+ commands (#16803)
- the default container rollout steps when
max_instancesis omitted (#16920)
The pull request consumes all three changesets: local-artifacts-event-ingress, containers-rollout-default-max-instances and autoconfig-native-vite-commands.
Changes since the last review:
@cloudflare/autoconfignow gets a minor bump, 0.12.1 → 0.13.0.- The Wrangler CHANGELOG has a patch entry for #16803.
- The
@cloudflare/vitest-pluginCHANGELOG now listsb219078among its updated dependencies.
These all match the changeset frontmatter (@cloudflare/autoconfig: minor, wrangler: patch). The remaining versions and CHANGELOG entries match the release notes in the description.
Reviewed commit: cbac50bb
cbac50b to
b64cf20
Compare
There was a problem hiding this comment.
Superseded by the review of
464846c7.
This review, of b64cf209
✅ Approved — Routine Changesets release. All four consumed changesets, including the newly added OAuth refresh fix (#16874), appear in the right CHANGELOGs, and the version bumps match the changeset levels and the dependency graph.
The decision is advisory: this review is a comment and never approves, blocks or requests changes on the pull request.
✅ All checks passed
🚀 Release: ✅ LGTM
Overall risk: Medium
This release brings together four behaviour changes:
| PR | Risk | Summary |
|---|---|---|
| #16246 | Medium | Local Artifacts events can now start Workflows. Affects miniflare, config, codemods, workers-utils and wrangler. |
| #16803 | Medium | Experimental projects now run with their installed Vite or Vite+ commands. Bumps autoconfig to minor and wrangler as a patch. |
| #16920 | Medium | Default container rollout steps change when max_instances is omitted. Patch for wrangler. |
| #16874 | Medium | OAuth refresh now re-reads credentials so it doesn't refresh again after a sibling process has already updated them. Patch for workers-auth and wrangler. |
Changes since the last review:
- The
recheck-oauth-expiry-before-refreshchangeset is now consumed. @cloudflare/workers-authis bumped 0.18.2 → 0.18.3, and its CHANGELOG has an entry for #16874.- The Wrangler CHANGELOG has a matching patch entry for #16874.
- The
@cloudflare/vitest-pluginand@cloudflare/remote-bindingsCHANGELOGs list4335eacamong their updated dependencies.
The versions and CHANGELOG entries match the release notes in the description.
Reviewed commit: b64cf209
b64cf20 to
464846c
Compare
There was a problem hiding this comment.
Superseded by the review of
719f6530.
This review, of 464846c7
✅ Approved — Routine Changesets release. All four consumed changesets, including the newly added OAuth refresh fix (#16874), appear in the right CHANGELOGs, and the version bumps match the changeset levels and the dependency graph.
The decision is advisory: this review is a comment and never approves, blocks or requests changes on the pull request.
✅ All checks passed
🚀 Release: ✅ LGTM
Overall risk: Medium
This release brings together four behaviour changes:
| PR | Risk | Summary |
|---|---|---|
| #16246 | Medium | Local Artifacts events can now start Workflows. Affects miniflare, config, codemods, workers-utils and wrangler. |
| #16803 | Medium | Experimental projects now run with their installed Vite or Vite+ commands. Bumps autoconfig to minor and wrangler as a patch. |
| #16920 | Medium | Default container rollout steps change when max_instances is omitted. Patch for wrangler. |
| #16874 | Medium | OAuth refresh now re-reads credentials so it doesn't refresh again after a sibling process has already updated them. Patch for workers-auth and wrangler. |
Changes since the last review:
- The
recheck-oauth-expiry-before-refreshchangeset is now consumed. @cloudflare/workers-authis bumped 0.18.2 → 0.18.3, and its CHANGELOG has an entry for #16874.- The Wrangler CHANGELOG has a matching patch entry for #16874.
- The
@cloudflare/vitest-pluginand@cloudflare/remote-bindingsCHANGELOGs list4335eacamong their updated dependencies.
The versions and CHANGELOG entries match the release notes in the description.
Reviewed commit: 464846c7 — same changes as b64cf209, so this is that commit's review (no new review was run; line numbers are as of b64cf209)
464846c to
719f653
Compare
There was a problem hiding this comment.
Superseded by the review of
2ea697b9.
This review, of 719f6530
✅ Approved — Routine Changesets release. All four consumed changesets, including the newly added OAuth refresh fix (#16874), appear in the right CHANGELOGs, and the version bumps match the changeset levels and the dependency graph.
The decision is advisory: this review is a comment and never approves, blocks or requests changes on the pull request.
✅ All checks passed
🚀 Release: ✅ LGTM
Overall risk: Medium
This release brings together four behaviour changes:
| PR | Risk | Summary |
|---|---|---|
| #16246 | Medium | Local Artifacts events can now start Workflows. Affects miniflare, config, codemods, workers-utils and wrangler. |
| #16803 | Medium | Experimental projects now run with their installed Vite or Vite+ commands. Bumps autoconfig to minor and wrangler as a patch. |
| #16920 | Medium | Default container rollout steps change when max_instances is omitted. Patch for wrangler. |
| #16874 | Medium | OAuth refresh now re-reads credentials so it doesn't refresh again after a sibling process has already updated them. Patch for workers-auth and wrangler. |
Changes since the last review:
- The
recheck-oauth-expiry-before-refreshchangeset is now consumed. @cloudflare/workers-authis bumped 0.18.2 → 0.18.3, and its CHANGELOG has an entry for #16874.- The Wrangler CHANGELOG has a matching patch entry for #16874.
- The
@cloudflare/vitest-pluginand@cloudflare/remote-bindingsCHANGELOGs list4335eacamong their updated dependencies.
The versions and CHANGELOG entries match the release notes in the description.
Reviewed commit: 719f6530 — same changes as b64cf209, so this is that commit's review (no new review was run; line numbers are as of b64cf209)
4b68f5c to
2ea697b
Compare
There was a problem hiding this comment.
Superseded by the review of
ee04ea58.
This review, of 2ea697b9
✅ Approved — Routine Changesets release. The four new create-cloudflare dependency-update changesets (#16933–#16936) are consumed into a 2.74.13 patch release with matching CHANGELOG entries. The rest of the release is unchanged from the previously approved state.
The decision is advisory: this review is a comment and never approves, blocks or requests changes on the pull request.
✅ All checks passed
🚀 Release: ✅ LGTM
Overall risk: Medium
This release brings together four behaviour changes and four patch-level dependency updates to create-cloudflare's framework tools:
| PR | Risk | Summary |
|---|---|---|
| #16246 | Medium | Local Artifacts events can now start Workflows. Affects miniflare, config, codemods, workers-utils and wrangler. |
| #16803 | Medium | Experimental projects now run with their installed Vite or Vite+ commands. Minor bump for autoconfig, patch for wrangler. |
| #16920 | Medium | Default container rollout steps change when max_instances is omitted. Patch for wrangler. |
| #16874 | Medium | OAuth refresh no longer refreshes again after a sibling process has already updated the credentials. Patch for workers-auth and wrangler. |
| #16933 | Low | Updates @angular/create 22.2.6 → 22.2.7 in create-cloudflare. |
| #16934 | Low | Updates create-qwik 1.20.3 → 1.20.4 in create-cloudflare. |
| #16935 | Low | Updates create-vike 0.0.692 → 0.0.694 in create-cloudflare. |
| #16936 | Low | Updates create-astro 5.3.1 → 5.3.2 in create-cloudflare. |
Changes since the last review:
- The four
c3-frameworks-update-*changesets are now consumed. create-cloudflareis bumped 2.74.12 → 2.74.13, and its CHANGELOG has an entry for each of the four updates.
The other package versions and CHANGELOG entries are unchanged since the last review and still match the release notes in the description.
Reviewed commit: 2ea697b9
2ea697b to
ee04ea5
Compare
There was a problem hiding this comment.
Superseded by the review of
17dacc53.
This review, of ee04ea58
✅ Approved — This is a routine Changesets release with consistent version bumps and CHANGELOG entries. The only change since the last approved state is the consumed #16937 create-analog dependency-update changeset.
The decision is advisory: this review is a comment and never approves, blocks or requests changes on the pull request.
✅ All checks passed
🚀 Release: ✅ LGTM
Overall risk: Medium
This release brings together four behaviour changes and five patch-level dependency updates to create-cloudflare's framework tools.
| PR | Risk | Summary |
|---|---|---|
| #16246 | Medium | Local Artifacts events can now start Workflows. Affects miniflare, config, codemods, workers-utils and wrangler. |
| #16803 | Medium | Experimental projects run with their installed Vite or Vite+ commands. Minor bump for autoconfig, patch for wrangler. |
| #16920 | Medium | Default container rollout steps now use the effective max_instances when it is omitted. Patch for wrangler. |
| #16874 | Medium | OAuth refresh no longer refreshes again after a sibling process has already updated the credentials. Patch for workers-auth and wrangler. |
| #16933 | Low | @angular/create 22.2.6 → 22.2.7 |
| #16934 | Low | create-qwik 1.20.3 → 1.20.4 |
| #16935 | Low | create-vike 0.0.692 → 0.0.694 |
| #16936 | Low | create-astro 5.3.1 → 5.3.2 |
| #16937 | Low | create-analog 2.9.6 → 2.9.7 |
Changes since the last review:
- The
c3-frameworks-update-16937changeset is now consumed. - The create-cloudflare 2.74.13 CHANGELOG now includes the
create-analogentry.
The other package versions and CHANGELOG entries have not changed and still match the release notes in the description.
Reviewed commit: ee04ea58
ee04ea5 to
17dacc5
Compare
There was a problem hiding this comment.
Superseded by the review of
287a4225.
This review, of 17dacc53
✅ Approved — This is a routine Changesets release with consistent version bumps and CHANGELOG entries. The only change since the last approved state is the consumed #16938 create-next-app changeset, now recorded in the create-cloudflare 2.74.13 CHANGELOG.
The decision is advisory: this review is a comment and never approves, blocks or requests changes on the pull request.
✅ All checks passed
🚀 Release: ✅ LGTM
Overall risk: Medium
This release has four behaviour changes and six patch-level dependency updates to create-cloudflare's framework tools.
| PR | Risk | Summary |
|---|---|---|
| #16246 | Medium | Local Artifacts events can now start Workflows. Affects miniflare, config, codemods, workers-utils and wrangler. |
| #16803 | Medium | Experimental projects run with their installed Vite or Vite+ commands. Minor bump for autoconfig, patch for wrangler. |
| #16920 | Medium | Default container rollout steps now use the effective max_instances when it is omitted. Patch for wrangler. |
| #16874 | Medium | OAuth refresh no longer runs again after a sibling process has already updated the credentials. Patch for workers-auth and wrangler. |
| #16933 | Low | @angular/create 22.2.6 → 22.2.7 |
| #16934 | Low | create-qwik 1.20.3 → 1.20.4 |
| #16935 | Low | create-vike 0.0.692 → 0.0.694 |
| #16936 | Low | create-astro 5.3.1 → 5.3.2 |
| #16937 | Low | create-analog 2.9.6 → 2.9.7 |
| #16938 | Low | create-next-app 16.4.5 → 16.4.6 |
Changes since the last review:
- The
c3-frameworks-update-16938changeset has been consumed. - The create-cloudflare 2.74.13 CHANGELOG now includes the
create-next-appentry.
No other package versions or CHANGELOG entries changed, and they still match the release notes in the description.
Reviewed commit: 17dacc53
17dacc5 to
287a422
Compare
There was a problem hiding this comment.
Superseded by the review of
18874949.
This review, of 287a4225
✅ Approved — This is a routine Changesets release with consistent version bumps and CHANGELOG entries. Since the last review, the only change is the consumed #16944 config-watch changeset, which is now recorded in the wrangler 4.163.0 CHANGELOG and in the dependency list of vitest-plugin 1.8.3.
The decision is advisory: this review is a comment and never approves, blocks or requests changes on the pull request.
✅ All checks passed
🚀 Release: ✅ LGTM
Overall risk: Medium
This release has five behaviour changes and six patch-level dependency updates to create-cloudflare's framework tools.
| PR | Risk | Summary |
|---|---|---|
| #16246 | Medium | Local Artifacts events can now start Workflows. Affects config, miniflare, codemods, workers-utils and wrangler. |
| #16803 | Medium | Experimental projects run with their installed Vite or Vite+ commands. Minor bump for autoconfig, patch for wrangler. |
| #16944 | Medium | wrangler dev no longer misses config file changes saved just after a reload. |
| #16920 | Medium | Default container rollout steps now use the effective max_instances when it is omitted. |
| #16874 | Medium | OAuth refresh no longer runs again after a sibling process has already updated the credentials. Patch for workers-auth and wrangler. |
| #16933 | Low | @angular/create 22.2.6 → 22.2.7 |
| #16934 | Low | create-qwik 1.20.3 → 1.20.4 |
| #16935 | Low | create-vike 0.0.692 → 0.0.694 |
| #16936 | Low | create-astro 5.3.1 → 5.3.2 |
| #16937 | Low | create-analog 2.9.6 → 2.9.7 |
| #16938 | Low | create-next-app 16.4.5 → 16.4.6 |
Changes since the last review:
Reviewed commit: 287a4225
287a422 to
1887494
Compare
There was a problem hiding this comment.
Superseded by the review of
da77cd65.
This review, of 18874949
✅ Approved — This is a routine Changesets release with consistent version bumps and CHANGELOG entries. Since the last review, the only change is the consumed #16944 config-watch changeset, which is now recorded in the wrangler 4.163.0 CHANGELOG and in the dependency list of vitest-plugin 1.8.3.
The decision is advisory: this review is a comment and never approves, blocks or requests changes on the pull request.
✅ All checks passed
🚀 Release: ✅ LGTM
Overall risk: Medium
This release has five behaviour changes and six patch-level dependency updates to create-cloudflare's framework tools.
| PR | Risk | Summary |
|---|---|---|
| #16246 | Medium | Local Artifacts events can now start Workflows. Affects config, miniflare, codemods, workers-utils and wrangler. |
| #16803 | Medium | Experimental projects run with their installed Vite or Vite+ commands. Minor bump for autoconfig, patch for wrangler. |
| #16944 | Medium | wrangler dev no longer misses config file changes saved just after a reload. |
| #16920 | Medium | Default container rollout steps now use the effective max_instances when it is omitted. |
| #16874 | Medium | OAuth refresh no longer runs again after a sibling process has already updated the credentials. Patch for workers-auth and wrangler. |
| #16933 | Low | @angular/create 22.2.6 → 22.2.7 |
| #16934 | Low | create-qwik 1.20.3 → 1.20.4 |
| #16935 | Low | create-vike 0.0.692 → 0.0.694 |
| #16936 | Low | create-astro 5.3.1 → 5.3.2 |
| #16937 | Low | create-analog 2.9.6 → 2.9.7 |
| #16938 | Low | create-next-app 16.4.5 → 16.4.6 |
Changes since the last review:
Reviewed commit: 18874949 — same changes as 287a4225, so this is that commit's review (no new review was run; line numbers are as of 287a4225)
1887494 to
da77cd6
Compare
There was a problem hiding this comment.
Superseded by the review of
a765e5d5.
This review, of da77cd65
✅ Approved — This is a routine Changesets release with consistent version bumps and CHANGELOG entries. The new #16946 entries (default compatibility date 2026-11-16, workerd 1.20261116.1) match the miniflare 5.20261116.0-beta and pages-functions 0.1.10 bumps.
The decision is advisory: this review is a comment and never approves, blocks or requests changes on the pull request.
✅ All checks passed
🚀 Release: ✅ LGTM
Overall risk: Medium
This release has six behaviour changes and six patch-level updates to the framework tools that create-cloudflare uses.
| PR | Risk | Summary |
|---|---|---|
| #16246 | Medium | Artifacts events can now start Workflows locally. Affects config, miniflare, codemods, workers-utils and wrangler. |
| #16803 | Medium | Experimental projects run with their installed Vite or Vite+ commands. Minor bump for autoconfig, patch for wrangler. |
| #16944 | Medium | wrangler dev no longer misses config file changes saved just after a reload. |
| #16920 | Medium | Default container rollout steps now use the effective max_instances when it is omitted. |
| #16946 | Medium | DEFAULT_COMPAT_DATE moves to 2026-11-16, and workerd / workers-types are bumped to 1.20261116.1 / ^5.20261116.1. |
| #16874 | Medium | OAuth refresh no longer runs again after a sibling process has already updated the credentials. |
| #16933 | Low | @angular/create 22.2.6 → 22.2.7 |
| #16934 | Low | create-qwik 1.20.3 → 1.20.4 |
| #16935 | Low | create-vike 0.0.692 → 0.0.694 |
| #16936 | Low | create-astro 5.3.1 → 5.3.2 |
| #16937 | Low | create-analog 2.9.6 → 2.9.7 |
| #16938 | Low | create-next-app 16.4.5 → 16.4.6 |
Changes since the last review:
- The #16946 changesets (compatibility date and dependency update) have been consumed. miniflare is now
5.20261116.0-beta, in line with workerd 1.20261116.1. @cloudflare/pages-functionsgets its own patch bump to 0.1.10 for the compatibility-date change.- Every affected package's CHANGELOG now has the #16946 entries.
Concerns: None.
Reviewed commit: da77cd65
da77cd6 to
a765e5d
Compare
There was a problem hiding this comment.
✅ Approved — This is a consistent Changesets release. The version bumps and CHANGELOG entries match the consumed changesets, including the new Build Output v1, config RC and Vite plugin RC entries, and nothing blocks it.
The decision is advisory: this review is a comment and never approves, blocks or requests changes on the pull request.
✅ All checks passed
🚀 Release: ✅ LGTM
Overall risk: Medium
This release brings in several changes:
@cloudflare/build-output-utilsand the producers that write its output move to Build Output v1.@cloudflare/configgets its 1.0 release candidate, which includes breaking API changes.- Artifacts events can now start Workflows locally.
- Wrangler and Vite behaviour changes.
The release notes describe all of these, and the package version bumps match the CHANGELOG entries.
| PR | Risk | Summary |
|---|---|---|
| #16917 | Medium | Build Output v1 format and producer metadata. Readers and writers change together, and the release notes describe both sides. |
| #16907 | Medium | Breaking field and type changes in the @cloudflare/config 1.0 release candidate, listed in the release notes. |
| #16246 | Medium | Artifacts events can start Workflows locally. The supported events and the limits are documented. |
| #16803 | Medium | Experimental projects run with their installed Vite or Vite+ commands. |
| #16921 | Medium | Publishes the Vite plugin release candidate and makes the tools that configure projects install it. |
| #16944 | Medium | wrangler dev no longer misses config changes saved around a reload. |
| #16920 | Medium | Default container rollout steps now use the effective max_instances when it is omitted. |
| #16946 | Medium | Default compatibility date 2026-11-16; workerd 1.20261116.1. |
| #16874 | Medium | OAuth refresh no longer runs again after a sibling process has updated the credentials. |
| #16933–#16938 | Low | Patch-level updates to the framework tools that create-cloudflare uses. |
Reviewed commit: a765e5d5
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@cloudflare/build-output-utils@1.0.0-rc.0
Major Changes
#16917
d36b39dThanks @jamesopstad! - Release the first1.0.0release candidate, which reads and writes Build Output v1Build Output now lives in
.cloudflare/output/v1/. Only the.cloudflare/output/v<N>/naming convention is permanent: a future breaking change to the format would use a new version directory.readBuildOutput()lists the version directories first and throws aBuildOutputErrorunless it finds exactly onev1directory. This means output written by an older or newer tool, or a stalev0tree left next to a fresh one, fails with a clear error instead of being misread or deployed.BuildOutputErrornow has acode(not-found,newer-version,older-version,multiple-versions,unknown-fieldsorinvalid) plusfoundVersions,supportedVersions,producerandunknownFields. Consumers can use these to show their own advice instead of parsing the message. When a config contains fields the reader doesn't support, the error lists each field and names the tool that wrote the output.The root
config.jsonnow nests account settings undersettings, which is left out when none are set, and can record the tool that wrote the output in an optionalproducerfield.writeRootConfig()takes an options object, matching the otherwrite*functions:Patch Changes
#16946
e97c9f8Thanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-16Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
Updated dependencies [
d36b39d,0bf81ac,e97c9f8,349fc4e]:@cloudflare/config@1.0.0-rc.0
Major Changes
#16907
0bf81acThanks @jamesopstad! - Release the 1.0 release candidateThis release finalises the binding and Worker field names, and includes breaking changes:
firstPartyWorkermoves from the Worker's top level toexperimental.firstPartyWorker.bindings.pipeline()takesstreamIdin place ofname. Set it to the ID of the Pipelines stream, not its name. Legacy pipelines aren't supported.bindings.k2()takesidin place ofstream. Set it to the ID of the K2 stream.bindings.analytics()is renamed tobindings.analyticsSql(). Its binding type changes from"analytics"to"analytics-sql". TheAnalyticsSQLBinding,AnalyticsSQLBindingOptionsandAnalyticsSQLBindingSchemaexports are renamed toAnalyticsSqlBinding,AnalyticsSqlBindingOptionsandAnalyticsSqlBindingSchema.KVBindingSchemaexport is renamed toKvBindingSchema.ConnectTriggerOptionsBasetype is no longer exported. UseConnectTriggerOptionsinstead.InputWorkerConfigtype is no longer exported. Usez.input<typeof WorkerConfigSchema>if you need it.InputandOutputprefixes are replaced by the public type names andBuildOutput:InputConfigSchema→CloudflareConfigSchema,ParsedInputConfig→ParsedCloudflareConfigInputSettingsSchema→SettingsSchema,ParsedInputSettingsConfig→ParsedSettingsInputWorkerSchema→WorkerConfigSchema,ParsedInputWorkerConfig→ParsedWorkerConfigInputContainerSchema→ContainerConfigSchema,ParsedInputContainerConfig→ParsedContainerConfigOutputRootConfigSchema→BuildOutputRootConfigSchema,ParsedOutputRootConfig→ParsedBuildOutputRootConfigOutputWorkerSchema→BuildOutputWorkerConfigSchema,ParsedOutputWorkerConfig→ParsedBuildOutputWorkerConfigOutputContainerSchema→BuildOutputContainerConfigSchema,ParsedOutputContainerConfig→ParsedBuildOutputContainerConfigSetting the old
nameorstreamfield fails with an error that names the replacement field. Editors also show both fields as deprecated.The schema no longer fills in defaults. A parsed config without Containers leaves
containersundefined instead of setting it to[], and a Container withoutmaxInstancesleaves it undefined instead of setting it to20. Deploying still uses 20 instances whenmaxInstancesisn't set.Queue consumer
maxConcurrencyno longer acceptsnull. Wrangler already rejected it.Minor Changes
#16917
d36b39dThanks @jamesopstad! - Nest settings under an optionalsettingsand add an optionalproducerinBuildOutputRootConfigSchemaThe root
config.jsonin Build Output v1 has the shape{ producer?, settings?, buildContext }.settingsholds the account settings fromcloudflare.config.ts, is validated strictly, and is left out when none are set.produceris{ name, version }for the tool that wrote the output and is used only in diagnostics. The newBuildOutputProducerSchemaandParsedBuildOutputProducerare also exported.#16246
349fc4eThanks @leostera! - Start local Workflows from Artifacts eventsDeclare Artifacts events on
exports.workflow({ name, events })incloudflare.config.tsto start the owning Workflow locally incf, Vite, and Workers Vitest. Wrangler configurations continue to usetriggers.events. Native config conversion derives those targets from the Workflow export, andcf migrateattaches existing event subscriptions to their matching Workflow exports.Local Artifacts namespaces publish the documented
cf.artifacts.*messages for repository create, import, fork, and delete operations and token creation and revocation. Successful create, import, and fork operations also publish the initial token-created event. Delivery follows the committed mutation, is unordered, and does not fail the repository operation if a destination rejects it. Push, clone, and fetch events are not yet published locally. This feature does not provide local Artifacts-to-queue subscriptions.Patch Changes
#16946
e97c9f8Thanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-16Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
@cloudflare/autoconfig@0.13.0
Minor Changes
#16803
b219078Thanks @petebacondarwin! - Run experimental cf projects with their installed Vite or Vite+ commandscf dev,cf build, and deployments that build your project can use Vite or Vite+ even when no framework command is detected. This removes the need for the internalcf-vitedelegate and supports dependencies declared and hoisted at the root of a configured workspace. A workspace application using a custom-named Vite config should declare@cloudflare/vite-pluginin its own manifest, or addviteorvite-plusas a dependency or dev dependency to identify its tooling; this keeps shared root tools from selecting Vite for non-Vite siblings. Configs passed later via--configare evaluated by Vite when the command runs. Existing framework commands keep their priority. Consumers resolve bare executables using the detectednodeModulesPathsin order, adding.binto each directory. Lookup stops at the validated workspace root; standalone applications use only their ownnode_modules/.bin.Project inspection can recognize an existing Cloudflare configuration before dependencies are installed. Running a command provides guidance when the required tools are missing or the plugin version does not support cf profiles (
>=2.0.0-beta.v.13 <3). Vite evaluates the project configuration when the command runs, including dynamic configs and custom config files. Repair guidance uses the project’s detected package manager. Automatic setup asks users to convert CommonJS.cjsand.ctsVite configs to ESM imports and exports in.mjsor.mtsbefore adding the ESM-only Cloudflare plugin. Native builds also work with the Windows shell. Pages migration safeguards, unsupported-framework setup checks, and Wrangler command selection retain their existing behavior.Patch Changes
#16921
6785363Thanks @jamesopstad! - Install the Vite plugin release candidate when configuring projects forcfConfiguring a Vite project for
cfnow installs@cloudflare/vite-plugin@^2.0.0-rc.0instead of^2.0.0-beta.v.0, so an existing lockfile can't keep a beta that doesn't support the generated configuration.#16946
e97c9f8Thanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-16Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
Updated dependencies [
d36b39d,0bf81ac,e97c9f8,349fc4e]:@cloudflare/codemods@0.8.0
Minor Changes
#16246
349fc4eThanks @leostera! - Start local Workflows from Artifacts eventsDeclare Artifacts events on
exports.workflow({ name, events })incloudflare.config.tsto start the owning Workflow locally incf, Vite, and Workers Vitest. Wrangler configurations continue to usetriggers.events. Native config conversion derives those targets from the Workflow export, andcf migrateattaches existing event subscriptions to their matching Workflow exports.Local Artifacts namespaces publish the documented
cf.artifacts.*messages for repository create, import, fork, and delete operations and token creation and revocation. Successful create, import, and fork operations also publish the initial token-created event. Delivery follows the committed mutation, is unordered, and does not fail the repository operation if a destination rejects it. Push, clone, and fetch events are not yet published locally. This feature does not provide local Artifacts-to-queue subscriptions.Patch Changes
#16907
0bf81acThanks @jamesopstad! - Generate the release candidate@cloudflare/configfield names inwrangler-to-cfThe codemod now writes:
first_party_workerasexperimental.firstPartyWorkerbindings.pipeline({ streamId })bindings.k2({ id })bindings.analyticsSql()A Pipelines binding that uses the deprecated
pipelinefield gets aSTREAM_IDplaceholder and a follow-up asking for the stream ID, because that field names a legacy pipeline, which@cloudflare/configdoesn't support.#16921
6785363Thanks @jamesopstad! - Install the Vite plugin release candidate inwrangler-to-cfThe Wrangler-to-cf migration now installs
@cloudflare/vite-plugin@^2.0.0-rc.0instead of thebetadist tag, which no longer receives new releases. It upgrades projects whose plugin is declared as a dist tag or resolves to a version older than the release candidate, since earlier betas don't support the generated configuration. The range also covers the stable v2 releases, so the migration no longer rewritespackage.jsonto a dist tag after installing.#16946
e97c9f8Thanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-16Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
miniflare@5.20261116.0-beta
Minor Changes
#16246
349fc4eThanks @leostera! - Start local Workflows from Artifacts eventsDeclare Artifacts events on
exports.workflow({ name, events })incloudflare.config.tsto start the owning Workflow locally incf, Vite, and Workers Vitest. Wrangler configurations continue to usetriggers.events. Native config conversion derives those targets from the Workflow export, andcf migrateattaches existing event subscriptions to their matching Workflow exports.Local Artifacts namespaces publish the documented
cf.artifacts.*messages for repository create, import, fork, and delete operations and token creation and revocation. Successful create, import, and fork operations also publish the initial token-created event. Delivery follows the committed mutation, is unordered, and does not fail the repository operation if a destination rejects it. Push, clone, and fetch events are not yet published locally. This feature does not provide local Artifacts-to-queue subscriptions.#16907
0bf81acThanks @jamesopstad! - Rename the Pipelines, K2 and Analytics SQLenvbinding fields to match@cloudflare/configConfig-style
envbindings now use these shapes:{ type: "pipeline", streamId }instead of{ type: "pipeline", name }{ type: "k2", id }instead of{ type: "k2", stream }{ type: "analytics-sql" }instead of{ type: "analytics" }Patch Changes
#16946
e97c9f8Thanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-16Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#16946
e97c9f8Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"The following dependency versions have been updated:
@cloudflare/vite-plugin@2.0.0-rc.0
Minor Changes
#16917
d36b39dThanks @jamesopstad! - Write Build Output to.cloudflare/output/v1/and record the producervite buildand the experimentalwrangler build --experimental-cf-build-outputnow write Build Output v1, with account settings nested undersettingsin the rootconfig.json. They also record themselves as theproducer, so readers can name the tool that wrote the output in error messages. Previews from Build Output read the account settings from their new location.#16921
6785363Thanks @jamesopstad! - Release Vite plugin v2 as a release candidateVite plugin v2 is now published as
2.0.0-rc.<n>under thercnpm tag. The deprecatedParsedInputConfigWithWorkertype has been removed; useCloudflareConfiginstead.#16907
0bf81acThanks @jamesopstad! - MakeWorkerConfigthe type accepted by auxiliary and prerender WorkerconfigWorkerConfigfrom@cloudflare/vite-pluginis now the parsed Worker configuration that auxiliary and prerender Workerconfigaccepts and returns, and that their callbacks receive asentryWorkerConfig. It previously re-exported thedefineConfig()Worker type from@cloudflare/config, which didn't type-check as an auxiliary Workerconfig. To type a Worker incloudflare.config.ts, importWorkerConfigfromcf/configinstead.Patch Changes
#16946
e97c9f8Thanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-16Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#16917
d36b39dThanks @jamesopstad! - Ask for a rebuild when preview finds missing or outdated Build OutputWhen preview finds no Build Output, Build Output in the older v0 format, or Build Output in more than one format, it now says to build the project and preview again, rather than suggesting an upgrade.
Updated dependencies [
d36b39d,d36b39d,0bf81ac,e97c9f8,e97c9f8,349fc4e,0bf81ac]:wrangler@4.163.0
Minor Changes
#16917
d36b39dThanks @jamesopstad! - Write Build Output to.cloudflare/output/v1/and record the producervite buildand the experimentalwrangler build --experimental-cf-build-outputnow write Build Output v1, with account settings nested undersettingsin the rootconfig.json. They also record themselves as theproducer, so readers can name the tool that wrote the output in error messages. Previews from Build Output read the account settings from their new location.#16246
349fc4eThanks @leostera! - Start local Workflows from Artifacts eventsDeclare Artifacts events on
exports.workflow({ name, events })incloudflare.config.tsto start the owning Workflow locally incf, Vite, and Workers Vitest. Wrangler configurations continue to usetriggers.events. Native config conversion derives those targets from the Workflow export, andcf migrateattaches existing event subscriptions to their matching Workflow exports.Local Artifacts namespaces publish the documented
cf.artifacts.*messages for repository create, import, fork, and delete operations and token creation and revocation. Successful create, import, and fork operations also publish the initial token-created event. Delivery follows the committed mutation, is unordered, and does not fail the repository operation if a destination rejects it. Push, clone, and fetch events are not yet published locally. This feature does not provide local Artifacts-to-queue subscriptions.Patch Changes
#16803
b219078Thanks @petebacondarwin! - Run experimental cf projects with their installed Vite or Vite+ commandscf dev,cf build, and deployments that build your project can use Vite or Vite+ even when no framework command is detected. This removes the need for the internalcf-vitedelegate and supports dependencies declared and hoisted at the root of a configured workspace. A workspace application using a custom-named Vite config should declare@cloudflare/vite-pluginin its own manifest, or addviteorvite-plusas a dependency or dev dependency to identify its tooling; this keeps shared root tools from selecting Vite for non-Vite siblings. Configs passed later via--configare evaluated by Vite when the command runs. Existing framework commands keep their priority. Consumers resolve bare executables using the detectednodeModulesPathsin order, adding.binto each directory. Lookup stops at the validated workspace root; standalone applications use only their ownnode_modules/.bin.Project inspection can recognize an existing Cloudflare configuration before dependencies are installed. Running a command provides guidance when the required tools are missing or the plugin version does not support cf profiles (
>=2.0.0-beta.v.13 <3). Vite evaluates the project configuration when the command runs, including dynamic configs and custom config files. Repair guidance uses the project’s detected package manager. Automatic setup asks users to convert CommonJS.cjsand.ctsVite configs to ESM imports and exports in.mjsor.mtsbefore adding the ESM-only Cloudflare plugin. Native builds also work with the Windows shell. Pages migration safeguards, unsupported-framework setup checks, and Wrangler command selection retain their existing behavior.#16944
db3c071Thanks @danlapid! - Stopwrangler devfrom missing config file changes made soon after a reloadwrangler devreplaced its config file watcher on every reload without waiting for the new one to start, so a change saved in that gap was never applied. It now keeps one watcher while the set of watched files is unchanged, and reports a config as applied only once its files are being watched. A second change saved within 50 ms of the previous one is no longer dropped either.#16920
81e56ddThanks @benbuzbee! - Use the effectivemax_instancesvalue when choosing the default container rollout stepsWhen
max_instanceswas omitted, Wrangler deployed 20 instances but chose rollout steps as if there were 0 instances, so the rollout used a single 100% step. Wrangler now uses[10, 100]for omittedmax_instances, while still using a single 100% step whenmax_instancesis 0 or 1.#16946
e97c9f8Thanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-16Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#16946
e97c9f8Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"The following dependency versions have been updated:
#16874
4335eacThanks @petebacondarwin! - Avoid redundant OAuth refreshes after a sibling process updates credentialsCheck access-token expiry and select the refresh token from the same fresh credential snapshot. When a sibling has already saved a valid access token, reuse it without another exchange or write. This prevents an unnecessary rotation that can let an older response overwrite a newer refresh token.
#16917
d36b39dThanks @jamesopstad! - Detect Cloudflare Build Output of any version before deployingwrangler deploy,wrangler versions uploadandwrangler previewrefuse to run in a project that has Cloudflare Build Output, because that output belongs tocf. Detection now looks for any.cloudflare/output/v<N>/directory rather than only the root config of the current version, so output left by an older or newercfis still caught.Updated dependencies [
e97c9f8,e97c9f8,349fc4e,0bf81ac]:@cloudflare/cli-shared-helpers@0.3.9
Patch Changes
#16946
e97c9f8Thanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-16Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
Updated dependencies [
e97c9f8,349fc4e]:@cloudflare/containers-shared@0.26.2
Patch Changes
#16946
e97c9f8Thanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-16Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
Updated dependencies [
d36b39d,d36b39d,0bf81ac,e97c9f8,349fc4e]:create-cloudflare@2.74.13
Patch Changes
#16917
d36b39dThanks @jamesopstad! - Find the deployed Worker's name in Build Output v1After
cf deploy, C3 reads the Worker's name from the Build Output to look up its workers.dev URL. It now reads.cloudflare/output/v1/, falling back to.cloudflare/output/v0/because C3 installscf@latest, which may still write v0.#16933
80f0e5bThanks @dependabot! - Update dependencies of "create-cloudflare"The following dependency versions have been updated:
#16934
6a6f10fThanks @dependabot! - Update dependencies of "create-cloudflare"The following dependency versions have been updated:
#16935
819ed90Thanks @dependabot! - Update dependencies of "create-cloudflare"The following dependency versions have been updated:
#16936
f518803Thanks @dependabot! - Update dependencies of "create-cloudflare"The following dependency versions have been updated:
#16937
4bca70bThanks @dependabot! - Update dependencies of "create-cloudflare"The following dependency versions have been updated:
#16938
c46d179Thanks @dependabot! - Update dependencies of "create-cloudflare"The following dependency versions have been updated:
#16946
e97c9f8Thanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-16Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
@cloudflare/deploy-helpers@0.27.1
Patch Changes
#16917
d36b39dThanks @jamesopstad! - Write Build Output to.cloudflare/output/v1/and record the producervite buildand the experimentalwrangler build --experimental-cf-build-outputnow write Build Output v1, with account settings nested undersettingsin the rootconfig.json. They also record themselves as theproducer, so readers can name the tool that wrote the output in error messages. Previews from Build Output read the account settings from their new location.#16946
e97c9f8Thanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-16Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
Updated dependencies [
d36b39d,0bf81ac,e97c9f8,e97c9f8,349fc4e,0bf81ac]:@cloudflare/pages-functions@0.1.10
Patch Changes
#16946
e97c9f8Thanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-16Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
@cloudflare/pages-shared@0.13.215
Patch Changes
#16946
e97c9f8Thanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-16Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
Updated dependencies [
e97c9f8,e97c9f8,349fc4e,0bf81ac]:@cloudflare/runtime-types@0.1.29
Patch Changes
#16946
e97c9f8Thanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-16Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
Updated dependencies [
e97c9f8,e97c9f8,349fc4e,0bf81ac]:@cloudflare/vitest-plugin@1.8.3
Patch Changes
#16946
e97c9f8Thanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-16Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
Updated dependencies [
b219078,d36b39d,db3c071,81e56dd,e97c9f8,e97c9f8,349fc4e,0bf81ac,4335eac,d36b39d]:@cloudflare/workers-auth@0.18.3
Patch Changes
#16946
e97c9f8Thanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-16Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#16874
4335eacThanks @petebacondarwin! - Avoid redundant OAuth refreshes after a sibling process updates credentialsCheck access-token expiry and select the refresh token from the same fresh credential snapshot. When a sibling has already saved a valid access token, reuse it without another exchange or write. This prevents an unnecessary rotation that can let an older response overwrite a newer refresh token.
Updated dependencies [
e97c9f8,349fc4e]:@cloudflare/workers-utils@0.54.1
Patch Changes
#16946
e97c9f8Thanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-16Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#16246
349fc4eThanks @leostera! - Start local Workflows from Artifacts eventsDeclare Artifacts events on
exports.workflow({ name, events })incloudflare.config.tsto start the owning Workflow locally incf, Vite, and Workers Vitest. Wrangler configurations continue to usetriggers.events. Native config conversion derives those targets from the Workflow export, andcf migrateattaches existing event subscriptions to their matching Workflow exports.Local Artifacts namespaces publish the documented
cf.artifacts.*messages for repository create, import, fork, and delete operations and token creation and revocation. Successful create, import, and fork operations also publish the initial token-created event. Delivery follows the committed mutation, is unordered, and does not fail the repository operation if a destination rejects it. Push, clone, and fetch events are not yet published locally. This feature does not provide local Artifacts-to-queue subscriptions.@cloudflare/remote-bindings@0.0.66
Patch Changes
d36b39d,e97c9f8,e97c9f8,349fc4e,0bf81ac,4335eac]: