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.- The
KVBindingSchemaexport is renamed toKvBindingSchema. - The
ConnectTriggerOptionsBasetype is no longer exported. UseConnectTriggerOptionsinstead. - The
InputWorkerConfigtype is no longer exported. Usez.input<typeof WorkerConfigSchema>if you need it. - The config schemas and their parsed types are renamed after what they describe. The
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→ParsedBuildOutputContainerConfig
Setting 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.