Skip to content

Version Packages - #16915

Merged
edmundhung merged 1 commit into
mainfrom
changeset-release/main
Nov 16, 2026
Merged

edmundhung merged 1 commit into
mainfrom
changeset-release/main

Conversation

@workers-devprod

@workers-devprod workers-devprod commented Nov 13, 2026 •

Copy link
Copy Markdown
Contributor

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 d36b39d Thanks @jamesopstad! - Release the first 1.0.0 release candidate, which reads and writes Build Output v1

    Build 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 a BuildOutputError unless it finds exactly one v1 directory. This means output written by an older or newer tool, or a stale v0 tree left next to a fresh one, fails with a clear error instead of being misread or deployed.

    BuildOutputError now has a code (not-found, newer-version, older-version, multiple-versions, unknown-fields or invalid) plus foundVersions, supportedVersions, producer and unknownFields. 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.json now nests account settings under settings, which is left out when none are set, and can record the tool that wrote the output in an optional producer field. writeRootConfig() takes an options object, matching the other write* functions:

    // Before
    await writeRootConfig(root, settings, buildContext);
    
    // After
    await writeRootConfig({
      root,
      settings,
      buildContext,
      producer: { name: "my-framework-adapter", version: "1.2.3" },
    });

Patch Changes

  • #16946 e97c9f8 Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-16

    Use 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

@cloudflare/config@1.0.0-rc.0

Major Changes

  • #16907 0bf81ac Thanks @jamesopstad! - Release the 1.0 release candidate

    This release finalises the binding and Worker field names, and includes breaking changes:

    • firstPartyWorker moves from the Worker's top level to experimental.firstPartyWorker.
    • bindings.pipeline() takes streamId in place of name. Set it to the ID of the Pipelines stream, not its name. Legacy pipelines aren't supported.
    • bindings.k2() takes id in place of stream. Set it to the ID of the K2 stream.
    • bindings.analytics() is renamed to bindings.analyticsSql(). Its binding type changes from "analytics" to "analytics-sql". The AnalyticsSQLBinding, AnalyticsSQLBindingOptions and AnalyticsSQLBindingSchema exports are renamed to AnalyticsSqlBinding, AnalyticsSqlBindingOptions and AnalyticsSqlBindingSchema.
    • The KVBindingSchema export is renamed to KvBindingSchema.
    • The ConnectTriggerOptionsBase type is no longer exported. Use ConnectTriggerOptions instead.
    • The InputWorkerConfig type is no longer exported. Use z.input<typeof WorkerConfigSchema> if you need it.
    • The config schemas and their parsed types are renamed after what they describe. The Input and Output prefixes are replaced by the public type names and BuildOutput:
      • InputConfigSchema → CloudflareConfigSchema, ParsedInputConfig → ParsedCloudflareConfig
      • InputSettingsSchema → SettingsSchema, ParsedInputSettingsConfig → ParsedSettings
      • InputWorkerSchema → WorkerConfigSchema, ParsedInputWorkerConfig → ParsedWorkerConfig
      • InputContainerSchema → ContainerConfigSchema, ParsedInputContainerConfig → ParsedContainerConfig
      • OutputRootConfigSchema → BuildOutputRootConfigSchema, ParsedOutputRootConfig → ParsedBuildOutputRootConfig
      • OutputWorkerSchema → BuildOutputWorkerConfigSchema, ParsedOutputWorkerConfig → ParsedBuildOutputWorkerConfig
      • OutputContainerSchema → BuildOutputContainerConfigSchema, ParsedOutputContainerConfig → ParsedBuildOutputContainerConfig

    Setting the old name or stream field 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 containers undefined instead of setting it to [], and a Container without maxInstances leaves it undefined instead of setting it to 20. Deploying still uses 20 instances when maxInstances isn't set.

    Queue consumer maxConcurrency no longer accepts null. Wrangler already rejected it.

Minor Changes

  • #16917 d36b39d Thanks @jamesopstad! - Nest settings under an optional settings and add an optional producer in BuildOutputRootConfigSchema

    The root config.json in Build Output v1 has the shape { producer?, settings?, buildContext }. settings holds the account settings from cloudflare.config.ts, is validated strictly, and is left out when none are set. producer is { name, version } for the tool that wrote the output and is used only in diagnostics. The new BuildOutputProducerSchema and ParsedBuildOutputProducer are also exported.

  • #16246 349fc4e Thanks @leostera! - Start local Workflows from Artifacts events

    Declare Artifacts events on exports.workflow({ name, events }) in cloudflare.config.ts to start the owning Workflow locally in cf, Vite, and Workers Vitest. Wrangler configurations continue to use triggers.events. Native config conversion derives those targets from the Workflow export, and cf migrate attaches 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 e97c9f8 Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-16

    Use 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 b219078 Thanks @petebacondarwin! - Run experimental cf projects with their installed Vite or Vite+ commands

    cf 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 internal cf-vite delegate 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-plugin in its own manifest, or add vite or vite-plus as 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 --config are evaluated by Vite when the command runs. Existing framework commands keep their priority. Consumers resolve bare executables using the detected nodeModulesPaths in order, adding .bin to each directory. Lookup stops at the validated workspace root; standalone applications use only their own node_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 .cjs and .cts Vite configs to ESM imports and exports in .mjs or .mts before 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 6785363 Thanks @jamesopstad! - Install the Vite plugin release candidate when configuring projects for cf

    Configuring a Vite project for cf now installs @cloudflare/vite-plugin@^2.0.0-rc.0 instead of ^2.0.0-beta.v.0, so an existing lockfile can't keep a beta that doesn't support the generated configuration.

  • #16946 e97c9f8 Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-16

    Use 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
    • @cloudflare/workers-utils@0.54.1
    • @cloudflare/cli-shared-helpers@0.3.9

@cloudflare/codemods@0.8.0

Minor Changes

  • #16246 349fc4e Thanks @leostera! - Start local Workflows from Artifacts events

    Declare Artifacts events on exports.workflow({ name, events }) in cloudflare.config.ts to start the owning Workflow locally in cf, Vite, and Workers Vitest. Wrangler configurations continue to use triggers.events. Native config conversion derives those targets from the Workflow export, and cf migrate attaches 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 0bf81ac Thanks @jamesopstad! - Generate the release candidate @cloudflare/config field names in wrangler-to-cf

    The codemod now writes:

    • first_party_worker as experimental.firstPartyWorker
    • Pipelines bindings as bindings.pipeline({ streamId })
    • K2 bindings as bindings.k2({ id })
    • the Analytics SQL binding as bindings.analyticsSql()

    A Pipelines binding that uses the deprecated pipeline field gets a STREAM_ID placeholder and a follow-up asking for the stream ID, because that field names a legacy pipeline, which @cloudflare/config doesn't support.

  • #16921 6785363 Thanks @jamesopstad! - Install the Vite plugin release candidate in wrangler-to-cf

    The Wrangler-to-cf migration now installs @cloudflare/vite-plugin@^2.0.0-rc.0 instead of the beta dist 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 rewrites package.json to a dist tag after installing.

  • #16946 e97c9f8 Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-16

    Use 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 349fc4e Thanks @leostera! - Start local Workflows from Artifacts events

    Declare Artifacts events on exports.workflow({ name, events }) in cloudflare.config.ts to start the owning Workflow locally in cf, Vite, and Workers Vitest. Wrangler configurations continue to use triggers.events. Native config conversion derives those targets from the Workflow export, and cf migrate attaches 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 0bf81ac Thanks @jamesopstad! - Rename the Pipelines, K2 and Analytics SQL env binding fields to match @cloudflare/config

    Config-style env bindings 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 e97c9f8 Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-16

    Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.

  • #16946 e97c9f8 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    @cloudflare/workers-types ^5.20261113.1 ^5.20261116.1
    workerd 1.20261113.1 1.20261116.1

@cloudflare/vite-plugin@2.0.0-rc.0

Minor Changes

  • #16917 d36b39d Thanks @jamesopstad! - Write Build Output to .cloudflare/output/v1/ and record the producer

    vite build and the experimental wrangler build --experimental-cf-build-output now write Build Output v1, with account settings nested under settings in the root config.json. They also record themselves as the producer, 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 6785363 Thanks @jamesopstad! - Release Vite plugin v2 as a release candidate

    Vite plugin v2 is now published as 2.0.0-rc.<n> under the rc npm tag. The deprecated ParsedInputConfigWithWorker type has been removed; use CloudflareConfig instead.

  • #16907 0bf81ac Thanks @jamesopstad! - Make WorkerConfig the type accepted by auxiliary and prerender Worker config

    WorkerConfig from @cloudflare/vite-plugin is now the parsed Worker configuration that auxiliary and prerender Worker config accepts and returns, and that their callbacks receive as entryWorkerConfig. It previously re-exported the defineConfig() Worker type from @cloudflare/config, which didn't type-check as an auxiliary Worker config. To type a Worker in cloudflare.config.ts, import WorkerConfig from cf/config instead.

Patch Changes

  • #16946 e97c9f8 Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-16

    Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.

  • #16917 d36b39d Thanks @jamesopstad! - Ask for a rebuild when preview finds missing or outdated Build Output

    When 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 d36b39d Thanks @jamesopstad! - Write Build Output to .cloudflare/output/v1/ and record the producer

    vite build and the experimental wrangler build --experimental-cf-build-output now write Build Output v1, with account settings nested under settings in the root config.json. They also record themselves as the producer, 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 349fc4e Thanks @leostera! - Start local Workflows from Artifacts events

    Declare Artifacts events on exports.workflow({ name, events }) in cloudflare.config.ts to start the owning Workflow locally in cf, Vite, and Workers Vitest. Wrangler configurations continue to use triggers.events. Native config conversion derives those targets from the Workflow export, and cf migrate attaches 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 b219078 Thanks @petebacondarwin! - Run experimental cf projects with their installed Vite or Vite+ commands

    cf 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 internal cf-vite delegate 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-plugin in its own manifest, or add vite or vite-plus as 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 --config are evaluated by Vite when the command runs. Existing framework commands keep their priority. Consumers resolve bare executables using the detected nodeModulesPaths in order, adding .bin to each directory. Lookup stops at the validated workspace root; standalone applications use only their own node_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 .cjs and .cts Vite configs to ESM imports and exports in .mjs or .mts before 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 db3c071 Thanks @danlapid! - Stop wrangler dev from missing config file changes made soon after a reload

    wrangler dev replaced 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 81e56dd Thanks @benbuzbee! - Use the effective max_instances value when choosing the default container rollout steps

    When max_instances was 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 omitted max_instances, while still using a single 100% step when max_instances is 0 or 1.

  • #16946 e97c9f8 Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-16

    Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.

  • #16946 e97c9f8 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    @cloudflare/workers-types ^5.20261113.1 ^5.20261116.1
    workerd 1.20261113.1 1.20261116.1
  • #16874 4335eac Thanks @petebacondarwin! - Avoid redundant OAuth refreshes after a sibling process updates credentials

    Check 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 d36b39d Thanks @jamesopstad! - Detect Cloudflare Build Output of any version before deploying

    wrangler deploy, wrangler versions upload and wrangler preview refuse to run in a project that has Cloudflare Build Output, because that output belongs to cf. 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 newer cf is still caught.

  • Updated dependencies [e97c9f8, e97c9f8, 349fc4e, 0bf81ac]:

@cloudflare/cli-shared-helpers@0.3.9

Patch Changes

  • #16946 e97c9f8 Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-16

    Use 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/workers-utils@0.54.1

@cloudflare/containers-shared@0.26.2

Patch Changes

  • #16946 e97c9f8 Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-16

    Use 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]:

    • @cloudflare/build-output-utils@1.0.0-rc.0
    • @cloudflare/config@1.0.0-rc.0
    • @cloudflare/workers-utils@0.54.1
    • @cloudflare/cli-shared-helpers@0.3.9

create-cloudflare@2.74.13

Patch Changes

  • #16917 d36b39d Thanks @jamesopstad! - Find the deployed Worker's name in Build Output v1

    After 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 installs cf@latest, which may still write v0.

  • #16933 80f0e5b Thanks @dependabot! - Update dependencies of "create-cloudflare"

    The following dependency versions have been updated:

    Dependency From To
    @angular/create 22.2.6 22.2.7
  • #16934 6a6f10f Thanks @dependabot! - Update dependencies of "create-cloudflare"

    The following dependency versions have been updated:

    Dependency From To
    create-qwik 1.20.3 1.20.4
  • #16935 819ed90 Thanks @dependabot! - Update dependencies of "create-cloudflare"

    The following dependency versions have been updated:

    Dependency From To
    create-vike 0.0.692 0.0.694
  • #16936 f518803 Thanks @dependabot! - Update dependencies of "create-cloudflare"

    The following dependency versions have been updated:

    Dependency From To
    create-astro 5.3.1 5.3.2
  • #16937 4bca70b Thanks @dependabot! - Update dependencies of "create-cloudflare"

    The following dependency versions have been updated:

    Dependency From To
    create-analog 2.9.6 2.9.7
  • #16938 c46d179 Thanks @dependabot! - Update dependencies of "create-cloudflare"

    The following dependency versions have been updated:

    Dependency From To
    create-next-app 16.4.5 16.4.6
  • #16946 e97c9f8 Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-16

    Use 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 d36b39d Thanks @jamesopstad! - Write Build Output to .cloudflare/output/v1/ and record the producer

    vite build and the experimental wrangler build --experimental-cf-build-output now write Build Output v1, with account settings nested under settings in the root config.json. They also record themselves as the producer, 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 e97c9f8 Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-16

    Use 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/config@1.0.0-rc.0
    • @cloudflare/workers-utils@0.54.1
    • @cloudflare/cli-shared-helpers@0.3.9
    • @cloudflare/containers-shared@0.26.2
    • miniflare@5.20261116.0-beta

@cloudflare/pages-functions@0.1.10

Patch Changes

  • #16946 e97c9f8 Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-16

    Use 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

@cloudflare/runtime-types@0.1.29

Patch Changes

@cloudflare/vitest-plugin@1.8.3

Patch Changes

@cloudflare/workers-auth@0.18.3

Patch Changes

  • #16946 e97c9f8 Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-16

    Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.

  • #16874 4335eac Thanks @petebacondarwin! - Avoid redundant OAuth refreshes after a sibling process updates credentials

    Check 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

@cloudflare/workers-utils@0.54.1

Patch Changes

  • #16946 e97c9f8 Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-16

    Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.

  • #16246 349fc4e Thanks @leostera! - Start local Workflows from Artifacts events

    Declare Artifacts events on exports.workflow({ name, events }) in cloudflare.config.ts to start the owning Workflow locally in cf, Vite, and Workers Vitest. Wrangler configurations continue to use triggers.events. Native config conversion derives those targets from the Workflow export, and cf migrate attaches 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

@devin-ai-integration devin-ai-integration Bot left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note

Newer findings are available below. Devin Review posted a newer report on this PR, in addition to the findings presented here.

Devin Review found 1 potential issue.

Devin Review

@clanky-the-clanker clanky-the-clanker Bot left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

@pkg-pr-new

pkg-pr-new Bot commented Nov 13, 2026 •

Copy link
Copy Markdown
@cloudflare/autoconfig

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

@cloudflare/build-output-utils

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

@cloudflare/codemods

npm i https://pkg.pr.new/@cloudflare/codemods@16915

@cloudflare/config

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

@cloudflare/containers-shared

npm i https://pkg.pr.new/@cloudflare/containers-shared@16915

create-cloudflare

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

@cloudflare/deploy-helpers

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

@cloudflare/kv-asset-handler

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

miniflare

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

@cloudflare/pages-functions

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

@cloudflare/pages-shared

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

@cloudflare/runtime-types

npm i https://pkg.pr.new/@cloudflare/runtime-types@16915

@cloudflare/unenv-preset

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

@cloudflare/vite-plugin

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

@cloudflare/vitest-plugin

npm i https://pkg.pr.new/@cloudflare/vitest-plugin@16915

@cloudflare/workers-auth

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

@cloudflare/workers-editor-shared

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

@cloudflare/workers-utils

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

wrangler

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

commit: a765e5d

devin-ai-integration[bot]

This comment was marked as resolved.

@clanky-the-clanker clanky-the-clanker Bot left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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) and miniflare (5.20261113.1-beta).
  • Patch: @cloudflare/workers-utils and 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

@clanky-the-clanker clanky-the-clanker Bot left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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_instances is 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/autoconfig now gets a minor bump, 0.12.1 → 0.13.0.
  • The Wrangler CHANGELOG has a patch entry for #16803.
  • The @cloudflare/vitest-plugin CHANGELOG now lists b219078 among 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

@clanky-the-clanker clanky-the-clanker Bot left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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-refresh changeset is now consumed.
  • @cloudflare/workers-auth is 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-plugin and @cloudflare/remote-bindings CHANGELOGs list 4335eac among their updated dependencies.

The versions and CHANGELOG entries match the release notes in the description.


Reviewed commit: b64cf209

@clanky-the-clanker clanky-the-clanker Bot left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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-refresh changeset is now consumed.
  • @cloudflare/workers-auth is 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-plugin and @cloudflare/remote-bindings CHANGELOGs list 4335eac among 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)

@clanky-the-clanker clanky-the-clanker Bot left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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-refresh changeset is now consumed.
  • @cloudflare/workers-auth is 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-plugin and @cloudflare/remote-bindings CHANGELOGs list 4335eac among 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)

@workers-devprod
workers-devprod force-pushed the changeset-release/main branch 4 times, most recently from 4b68f5c to 2ea697b Compare November 15, 2026 08:06

@clanky-the-clanker clanky-the-clanker Bot left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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-cloudflare is 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

@clanky-the-clanker clanky-the-clanker Bot left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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-16937 changeset is now consumed.
  • The create-cloudflare 2.74.13 CHANGELOG now includes the create-analog entry.

The other package versions and CHANGELOG entries have not changed and still match the release notes in the description.


Reviewed commit: ee04ea58

@clanky-the-clanker clanky-the-clanker Bot left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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-16938 changeset has been consumed.
  • The create-cloudflare 2.74.13 CHANGELOG now includes the create-next-app entry.

No other package versions or CHANGELOG entries changed, and they still match the release notes in the description.


Reviewed commit: 17dacc53

@clanky-the-clanker clanky-the-clanker Bot left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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:

  • The config-watch-lost-changes changeset (#16944) has been consumed.
  • The wrangler 4.163.0 CHANGELOG now has the #16944 entry, and the vitest-plugin 1.8.3 CHANGELOG lists db3c071 among its updated dependencies.

Reviewed commit: 287a4225

@clanky-the-clanker clanky-the-clanker Bot left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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:

  • The config-watch-lost-changes changeset (#16944) has been consumed.
  • The wrangler 4.163.0 CHANGELOG now has the #16944 entry, and the vitest-plugin 1.8.3 CHANGELOG lists db3c071 among its updated dependencies.

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)

@clanky-the-clanker clanky-the-clanker Bot left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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-functions gets 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

@clanky-the-clanker clanky-the-clanker Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ 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-utils and the producers that write its output move to Build Output v1.
  • @cloudflare/config gets 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

@edmundhung
edmundhung merged commit 06acbd4 into main Nov 16, 2026
115 of 118 checks passed
@edmundhung
edmundhung deleted the changeset-release/main branch November 16, 2026 11:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants