Repository navigation
Version Packages - #15828
Merged
Merged
Version Packages#15828
Conversation
@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: |
workers-devprod
force-pushed
the
changeset-release/main
branch
from
September 24, 2026 11:21
bc6d065 to
0651053
Compare
workers-devprod
force-pushed
the
changeset-release/main
branch
8 times, most recently
from
September 24, 2026 18:03
10bedd0 to
6fc17e2
Compare
workers-devprod
force-pushed
the
changeset-release/main
branch
from
September 24, 2026 19:03
6fc17e2 to
5e4ffad
Compare
dario-piotrowicz
approved these changes
Sep 24, 2026
Wichtowski
pushed a commit
to Wichtowski/workers-sdk
that referenced
this pull request
Sep 24, 2026
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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@0.8.0
Minor Changes
#15844
43f7ffbThanks @jamesopstad! - Allow frameworks to remove Worker bundles after prerenderingBuild Output readers now ignore stale manifests when only static assets remain and omit non-default Workers that have neither a bundle nor assets. A default Worker must still contain deployable output.
Patch Changes
bdda4c3,fc3cbaa]:@cloudflare/config@0.18.0
Minor Changes
#15786
bdda4c3Thanks @ThomasRubini! - Support UDP connect handlers in local developmentThe experimental
connectconfiguration now acceptsprotocol: "udp", with optionalidle_timeout_msandmax_pending_bytessettings. UDP datagrams are delivered to the Worker'sconnect()handler using workerd's value-mode socket streams, and can be tested withMiniflare#dispatchConnect({ protocol: "udp" }).#15779
fc3cbaaThanks @Naapperas! - Supportworkflowentries in theexportsconfiguration mapA Worker can now declare the Workflows it defines in
exports, keyed by theWorkflowEntrypointclass name:{ "exports": { "MyWorkflow": { "type": "workflow", "name": "my-workflow", "limits": { "steps": 100 }, "schedules": "0 * * * *" } } }A
workflowexport accepts the same settings as aworkflowsbinding:limits,concurrency,schedules, anddefault_retention.wrangler deployandwrangler versions uploadsend these entries to the upload API by name, andwrangler deployandwrangler triggers deployprovision the Workflow with its settings, just as they do forworkflowsbindings owned by the Worker. A Workflow may be declared both as a binding and as an export, as long as both declarations use the same class and do not set the same setting to different values. A binding to another Worker's Workflow cannot share a name with an export.@cloudflare/configadds the matchingexports.workflow()helper. Local development does not yet act on these entries.@cloudflare/containers-shared@0.20.0
Minor Changes
#15792
479e1e8Thanks @flakey5! - Configure SSH for experimental Durable Object-managed ContainersSet
containers[].sshandcontainers[].authorized_keyswhen usingscheduling_policy: "durable_object". These are application-wide settings that follow the same rules as the existing Durable Object-managed Container settings: normal deployments create missing applications and update explicitly configured values, while omitted settings preserve the existing application configuration.Patch Changes
479e1e8,43f7ffb,15799d4,bdda4c3,fc3cbaa]:@cloudflare/deploy-helpers@0.16.0
Minor Changes
#15792
479e1e8Thanks @flakey5! - Configure SSH for experimental Durable Object-managed ContainersSet
containers[].sshandcontainers[].authorized_keyswhen usingscheduling_policy: "durable_object". These are application-wide settings that follow the same rules as the existing Durable Object-managed Container settings: normal deployments create missing applications and update explicitly configured values, while omitted settings preserve the existing application configuration.#15779
fc3cbaaThanks @Naapperas! - Supportworkflowentries in theexportsconfiguration mapA Worker can now declare the Workflows it defines in
exports, keyed by theWorkflowEntrypointclass name:{ "exports": { "MyWorkflow": { "type": "workflow", "name": "my-workflow", "limits": { "steps": 100 }, "schedules": "0 * * * *" } } }A
workflowexport accepts the same settings as aworkflowsbinding:limits,concurrency,schedules, anddefault_retention.wrangler deployandwrangler versions uploadsend these entries to the upload API by name, andwrangler deployandwrangler triggers deployprovision the Workflow with its settings, just as they do forworkflowsbindings owned by the Worker. A Workflow may be declared both as a binding and as an export, as long as both declarations use the same class and do not set the same setting to different values. A binding to another Worker's Workflow cannot share a name with an export.@cloudflare/configadds the matchingexports.workflow()helper. Local development does not yet act on these entries.Patch Changes
52c0e9f,44f5295,be72815,479e1e8,940c692,15799d4,bdda4c3,fc3cbaa]:miniflare@5.20260923.0-alpha
Minor Changes
#15648
52c0e9fThanks @tpmmorris! - Expose configured Cron Triggers and one-off scheduled dispatch through Local ExplorerMiniflare's V4 Worker options now accept exact Cron Trigger expressions. Local Explorer reports them in Worker metadata and can dispatch a scheduled event to an exact local or peer Worker name with a chosen cron expression and time.
#15652
44f5295Thanks @tpmmorris! - Package the Cron Triggers interface in Local ExplorerThe Local Explorer assets now include an interactive Cron Triggers destination for one-off local scheduled-handler testing.
#15786
bdda4c3Thanks @ThomasRubini! - Support UDP connect handlers in local developmentThe experimental
connectconfiguration now acceptsprotocol: "udp", with optionalidle_timeout_msandmax_pending_bytessettings. UDP datagrams are delivered to the Worker'sconnect()handler using workerd's value-mode socket streams, and can be tested withMiniflare#dispatchConnect({ protocol: "udp" }).#15779
fc3cbaaThanks @Naapperas! - Supportworkflowentries in theexportsconfiguration mapA Worker can now declare the Workflows it defines in
exports, keyed by theWorkflowEntrypointclass name:{ "exports": { "MyWorkflow": { "type": "workflow", "name": "my-workflow", "limits": { "steps": 100 }, "schedules": "0 * * * *" } } }A
workflowexport accepts the same settings as aworkflowsbinding:limits,concurrency,schedules, anddefault_retention.wrangler deployandwrangler versions uploadsend these entries to the upload API by name, andwrangler deployandwrangler triggers deployprovision the Workflow with its settings, just as they do forworkflowsbindings owned by the Worker. A Workflow may be declared both as a binding and as an export, as long as both declarations use the same class and do not set the same setting to different values. A binding to another Worker's Workflow cannot share a name with an export.@cloudflare/configadds the matchingexports.workflow()helper. Local development does not yet act on these entries.Patch Changes
#15796
be72815Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"The following dependency versions have been updated:
#14847
940c692Thanks @TheSaiEaranti! - Emulate the deterministic-ID uniqueness contract in the local Workflows bindingThe local Workflows binding now matches the documented production behavior for deterministic instance IDs:
create({ id })with an ID that already exists throws(instance.already_exists)and retains the existing instance, andcreateBatch()skips IDs that already exist or repeat within the batch, excluding them from the result instead of creating duplicate executions. Previously both paths silently created duplicates, so code relying on deterministic IDs for idempotency (for example a Queue consumer creating one workflow per message) appeared to work locally while double-executing workflow bodies.@cloudflare/vite-plugin@1.60.0
Minor Changes
#15648
52c0e9fThanks @tpmmorris! - Advertise Local Explorer scheduled invocations to headless agentsThe Vite plugin's Local Explorer hint now documents how to invoke a Worker's scheduled handler and points agents to the OpenAPI schema for the complete request contract.
Patch Changes
52c0e9f,44f5295,be72815,479e1e8,940c692,52c0e9f,cd60c9c,15799d4,bdda4c3,fc3cbaa]:@cloudflare/workers-utils@0.42.0
Minor Changes
#15792
479e1e8Thanks @flakey5! - Configure SSH for experimental Durable Object-managed ContainersSet
containers[].sshandcontainers[].authorized_keyswhen usingscheduling_policy: "durable_object". These are application-wide settings that follow the same rules as the existing Durable Object-managed Container settings: normal deployments create missing applications and update explicitly configured values, while omitted settings preserve the existing application configuration.#15786
bdda4c3Thanks @ThomasRubini! - Support UDP connect handlers in local developmentThe experimental
connectconfiguration now acceptsprotocol: "udp", with optionalidle_timeout_msandmax_pending_bytessettings. UDP datagrams are delivered to the Worker'sconnect()handler using workerd's value-mode socket streams, and can be tested withMiniflare#dispatchConnect({ protocol: "udp" }).#15779
fc3cbaaThanks @Naapperas! - Supportworkflowentries in theexportsconfiguration mapA Worker can now declare the Workflows it defines in
exports, keyed by theWorkflowEntrypointclass name:{ "exports": { "MyWorkflow": { "type": "workflow", "name": "my-workflow", "limits": { "steps": 100 }, "schedules": "0 * * * *" } } }A
workflowexport accepts the same settings as aworkflowsbinding:limits,concurrency,schedules, anddefault_retention.wrangler deployandwrangler versions uploadsend these entries to the upload API by name, andwrangler deployandwrangler triggers deployprovision the Workflow with its settings, just as they do forworkflowsbindings owned by the Worker. A Workflow may be declared both as a binding and as an export, as long as both declarations use the same class and do not set the same setting to different values. A binding to another Worker's Workflow cannot share a name with an export.@cloudflare/configadds the matchingexports.workflow()helper. Local development does not yet act on these entries.Patch Changes
#15838
15799d4Thanks @oddharsh! - Updatesmol-tomlto 1.9.0 to fix slow parsing of very large TOML filesParse time for TOML config files now grows linearly with their size, instead of with its square: a 40,000-line file that took 259 ms to parse now takes 17 ms, while typical
wrangler.tomlfiles parse in the same time as before. This addresses theGHSA-r4xh-jqrq-34v2advisory against earlier versions of the parser.Some TOML syntax errors now point at the character that caused them. For example, a
wrangler.tomlcontainingINVALID "FILEis now reported asillegal character in keyat the", rather thanincomplete key-valueat the start of the line.wrangler@4.139.0
Minor Changes
#15792
479e1e8Thanks @flakey5! - Configure SSH for experimental Durable Object-managed ContainersSet
containers[].sshandcontainers[].authorized_keyswhen usingscheduling_policy: "durable_object". These are application-wide settings that follow the same rules as the existing Durable Object-managed Container settings: normal deployments create missing applications and update explicitly configured values, while omitted settings preserve the existing application configuration.#15648
52c0e9fThanks @tpmmorris! - Expose configured Cron Triggers to local development consumersWrangler now passes the active environment's exact Cron Trigger expressions to Miniflare so Local Explorer can display them. Headless agent sessions also advertise the Local Explorer scheduled invocation API.
#15786
bdda4c3Thanks @ThomasRubini! - Support UDP connect handlers in local developmentThe experimental
connectconfiguration now acceptsprotocol: "udp", with optionalidle_timeout_msandmax_pending_bytessettings. UDP datagrams are delivered to the Worker'sconnect()handler using workerd's value-mode socket streams, and can be tested withMiniflare#dispatchConnect({ protocol: "udp" }).#15779
fc3cbaaThanks @Naapperas! - Supportworkflowentries in theexportsconfiguration mapA Worker can now declare the Workflows it defines in
exports, keyed by theWorkflowEntrypointclass name:{ "exports": { "MyWorkflow": { "type": "workflow", "name": "my-workflow", "limits": { "steps": 100 }, "schedules": "0 * * * *" } } }A
workflowexport accepts the same settings as aworkflowsbinding:limits,concurrency,schedules, anddefault_retention.wrangler deployandwrangler versions uploadsend these entries to the upload API by name, andwrangler deployandwrangler triggers deployprovision the Workflow with its settings, just as they do forworkflowsbindings owned by the Worker. A Workflow may be declared both as a binding and as an export, as long as both declarations use the same class and do not set the same setting to different values. A binding to another Worker's Workflow cannot share a name with an export.@cloudflare/configadds the matchingexports.workflow()helper. Local development does not yet act on these entries.Patch Changes
#15796
be72815Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"The following dependency versions have been updated:
#14847
940c692Thanks @TheSaiEaranti! - Emulate the deterministic-ID uniqueness contract in the local Workflows bindingThe local Workflows binding now matches the documented production behavior for deterministic instance IDs:
create({ id })with an ID that already exists throws(instance.already_exists)and retains the existing instance, andcreateBatch()skips IDs that already exist or repeat within the batch, excluding them from the result instead of creating duplicate executions. Previously both paths silently created duplicates, so code relying on deterministic IDs for idempotency (for example a Queue consumer creating one workflow per message) appeared to work locally while double-executing workflow bodies.#15803
cd60c9cThanks @pmiguel! - Show--jurisdictionin help forwrangler kv namespace createThe option was supported but omitted from the command's help output. Users can now discover how to create KV namespaces in a specific jurisdiction.
#15838
15799d4Thanks @oddharsh! - Updatesmol-tomlto 1.9.0 to fix slow parsing of very large TOML filesParse time for TOML config files now grows linearly with their size, instead of with its square: a 40,000-line file that took 259 ms to parse now takes 17 ms, while typical
wrangler.tomlfiles parse in the same time as before. This addresses theGHSA-r4xh-jqrq-34v2advisory against earlier versions of the parser.Some TOML syntax errors now point at the character that caused them. For example, a
wrangler.tomlcontainingINVALID "FILEis now reported asillegal character in keyat the", rather thanincomplete key-valueat the start of the line.Updated dependencies [
52c0e9f,44f5295,be72815,940c692,bdda4c3,fc3cbaa]:@cloudflare/autoconfig@0.6.4
Patch Changes
479e1e8,15799d4,bdda4c3,fc3cbaa]:@cloudflare/cli-shared-helpers@0.1.38
Patch Changes
479e1e8,15799d4,bdda4c3,fc3cbaa]:create-cloudflare@2.72.12
Patch Changes
#15838
15799d4Thanks @oddharsh! - Updatesmol-tomlto 1.9.0 to fix slow parsing of very large TOML filesParse time for TOML config files now grows linearly with their size, instead of with its square: a 40,000-line file that took 259 ms to parse now takes 17 ms, while typical
wrangler.tomlfiles parse in the same time as before. This addresses theGHSA-r4xh-jqrq-34v2advisory against earlier versions of the parser.Some TOML syntax errors now point at the character that caused them. For example, a
wrangler.tomlcontainingINVALID "FILEis now reported asillegal character in keyat the", rather thanincomplete key-valueat the start of the line.@cloudflare/pages-shared@0.13.188
Patch Changes
52c0e9f,44f5295,be72815,940c692,bdda4c3,fc3cbaa]:@cloudflare/runtime-types@0.1.2
Patch Changes
52c0e9f,44f5295,be72815,940c692,bdda4c3,fc3cbaa]:@cloudflare/vitest-plugin@1.2.6
Patch Changes
52c0e9f,44f5295,be72815,479e1e8,940c692,52c0e9f,cd60c9c,15799d4,bdda4c3,fc3cbaa]:@cloudflare/workers-auth@0.9.2
Patch Changes
#15838
15799d4Thanks @oddharsh! - Updatesmol-tomlto 1.9.0 to fix slow parsing of very large TOML filesParse time for TOML config files now grows linearly with their size, instead of with its square: a 40,000-line file that took 259 ms to parse now takes 17 ms, while typical
wrangler.tomlfiles parse in the same time as before. This addresses theGHSA-r4xh-jqrq-34v2advisory against earlier versions of the parser.Some TOML syntax errors now point at the character that caused them. For example, a
wrangler.tomlcontainingINVALID "FILEis now reported asillegal character in keyat the", rather thanincomplete key-valueat the start of the line.Updated dependencies [
479e1e8,15799d4,bdda4c3,fc3cbaa]:@cloudflare/local-explorer-ui@0.17.0
Minor Changes
#15652
44f5295Thanks @tpmmorris! - Add one-off Cron Trigger testing to Local ExplorerDevelopers can invoke a Worker's configured or custom Cron Trigger with an exact or guided expression, choose a UTC or epoch-millisecond scheduled time, and inspect the latest structured result without editing configuration.
@cloudflare/remote-bindings@0.0.34
Patch Changes
52c0e9f,44f5295,be72815,479e1e8,940c692,15799d4,bdda4c3,fc3cbaa]: