Skip to content

Version Packages - #15710

Open
workers-devprod wants to merge 1 commit into
mainfrom
changeset-release/main
Open

workers-devprod wants to merge 1 commit into
mainfrom
changeset-release/main

Conversation

@workers-devprod

@workers-devprod workers-devprod commented Sep 18, 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/deploy-helpers@0.14.0

Minor Changes

  • #15699 45b3b81 Thanks @skepticfx! - Remove the experimental Container image environment binding

    Durable Object-managed Containers now use ctx.container.images without Wrangler generating env.EXPERIMENTAL_CLOUDFLARE_CONTAINER_IMAGES. Update code using the experimental environment binding to read ctx.container.images and regenerate your Worker types.

    Version deployments identify managed applications from native named images, and --containers-rollout=none preserves native Container metadata. Containers without named images must first be provisioned with wrangler deploy; versions upload verifies that their applications already exist. The old binding is no longer read or reserved, including on previously uploaded versions. keep_vars retains existing variables as usual; redeploy without it to remove an existing experimental binding.

Patch Changes

@cloudflare/workers-utils@0.41.0

Minor Changes

  • #15699 45b3b81 Thanks @skepticfx! - Remove the experimental Container image environment binding

    Durable Object-managed Containers now use ctx.container.images without Wrangler generating env.EXPERIMENTAL_CLOUDFLARE_CONTAINER_IMAGES. Update code using the experimental environment binding to read ctx.container.images and regenerate your Worker types.

    Version deployments identify managed applications from native named images, and --containers-rollout=none preserves native Container metadata. Containers without named images must first be provisioned with wrangler deploy; versions upload verifies that their applications already exist. The old binding is no longer read or reserved, including on previously uploaded versions. keep_vars retains existing variables as usual; redeploy without it to remove an existing experimental binding.

wrangler@4.136.0

Minor Changes

  • #15699 45b3b81 Thanks @skepticfx! - Remove the experimental Container image environment binding

    Durable Object-managed Containers now use ctx.container.images without Wrangler generating env.EXPERIMENTAL_CLOUDFLARE_CONTAINER_IMAGES. Update code using the experimental environment binding to read ctx.container.images and regenerate your Worker types.

    Version deployments identify managed applications from native named images, and --containers-rollout=none preserves native Container metadata. Containers without named images must first be provisioned with wrangler deploy; versions upload verifies that their applications already exist. The old binding is no longer read or reserved, including on previously uploaded versions. keep_vars retains existing variables as usual; redeploy without it to remove an existing experimental binding.

  • #15702 8235e6a Thanks @podonnell-dev! - Return structured configuration errors from wrangler preview --json

    When a Worker is missing its Preview configuration, JSON mode now returns an error, a suggested_config patch, and any associated onboarding messages without interactive output or terminal formatting. This changes the private-beta Preview command to make automated onboarding reliable.

  • #15577 731a2ee Thanks @sdnts! - Add support for jurisdictions to Queues subcommands

Patch Changes

  • #15440 43b1f85 Thanks @HuzaifaAbdulRehman! - Rebase absolute non-JavaScript module specifiers when preserve_file_names is enabled

    With preserve_file_names set, a non-JS module imported by an absolute path kept that path as its module name. The build machine's filesystem layout ended up inside the deployed Worker, and the module was never written to --outdir. A local dry run reported success while the upload failed server-side with error code 10021. Tooling that rewrites externals to absolute paths hits this, which is how it was found in @opennextjs/cloudflare with WASM imports.

    Absolute specifiers are now rebased to ./<basename>, which is what the hashed branch of the same code already does minus the hash prefix. Relative specifiers keep the behaviour they had.

  • Updated dependencies []:

@cloudflare/autoconfig@0.5.2

Patch Changes

  • Updated dependencies [45b3b81]:
    • @cloudflare/workers-utils@0.41.0
    • @cloudflare/cli-shared-helpers@0.1.35
    • @cloudflare/config@0.15.0

@cloudflare/cli-shared-helpers@0.1.35

Patch Changes

  • Updated dependencies [45b3b81]:
    • @cloudflare/workers-utils@0.41.0

@cloudflare/containers-shared@0.17.1

Patch Changes

  • Updated dependencies [45b3b81]:
    • @cloudflare/workers-utils@0.41.0
    • @cloudflare/build-output-utils@0.6.0
    • @cloudflare/cli-shared-helpers@0.1.35
    • @cloudflare/config@0.15.0

@cloudflare/vite-plugin@1.56.1

Patch Changes

@cloudflare/vitest-plugin@1.1.14

Patch Changes

@cloudflare/workers-auth@0.7.4

Patch Changes

  • Updated dependencies [45b3b81]:
    • @cloudflare/workers-utils@0.41.0

@cloudflare/remote-bindings@0.0.29

Patch Changes

devin-ai-integration[bot]

This comment was marked as resolved.

@pkg-pr-new

pkg-pr-new Bot commented Sep 18, 2026

Copy link
Copy Markdown
@cloudflare/autoconfig

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

@cloudflare/build-output-utils

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

@cloudflare/codemods

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

@cloudflare/config

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

@cloudflare/containers-shared

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

create-cloudflare

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

@cloudflare/deploy-helpers

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

@cloudflare/kv-asset-handler

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

miniflare

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

@cloudflare/pages-functions

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

@cloudflare/pages-shared

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

@cloudflare/unenv-preset

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

@cloudflare/vite-plugin

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

@cloudflare/vitest-plugin

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

@cloudflare/workers-auth

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

@cloudflare/workers-editor-shared

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

@cloudflare/workers-utils

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

wrangler

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

commit: 1394fdd

@workers-devprod
workers-devprod force-pushed the changeset-release/main branch 2 times, most recently from a05b4ce to 53bdff6 Compare September 18, 2026 18:22
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.

1 participant