Repository navigation
Version Packages - #16358
Merged
Merged
Version Packages#16358
Conversation
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
|
✅ Approved — No findings. This is a routine Changesets release: the version bumps match the new CHANGELOG entries and the release notes. The decision is advisory: this comment never approves, blocks or requests changes on the pull request. ✅ All checks passed🚀 Release: ✅ LGTMRisk: Low. These are standard Changesets patch releases across the affected packages. 🔒 Security: ✅ LGTMThere are no code changes. The pull request only bumps versions and updates changelogs. 📖 AGENTS.md: ✅ LGTMNo AGENTS.md updates are needed for a release pull request. 📋 Code Quality: ✅ LGTMEach ⚡ Performance: ✅ LGTMNo performance-relevant changes. 📝 Documentation: ✅ LGTMThe CHANGELOG entries are consistent with the removed changesets. Reviewed commit: |
@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
6 times, most recently
from
October 20, 2026 09:19
855c755 to
62c7040
Compare
workers-devprod
force-pushed
the
changeset-release/main
branch
from
October 20, 2026 10:46
62c7040 to
afae817
Compare
NuroDev
approved these changes
Oct 20, 2026
2 of 5 tasks
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
2 participants
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/autoconfig@0.7.11
Patch Changes
017bf9b]:@cloudflare/cli-shared-helpers@0.2.7
Patch Changes
017bf9b]:@cloudflare/containers-shared@0.23.1
Patch Changes
017bf9b]:create-cloudflare@2.74.2
Patch Changes
#16259
017bf9bThanks @NuroDev! - Use Vitest 5 in newly generated Workers projectsWorkers templates now install Vitest 5 and require @cloudflare/vitest-plugin 1.4.3 or newer, which supports Vitest's filesystem module cache.
@cloudflare/deploy-helpers@0.22.1
Patch Changes
#16370
61fc739Thanks @WalshyDev! - Fetch the remote config diff from the configured compliance regionWhen a Worker was last deployed from the dashboard,
wrangler deployandwrangler versions uploaddownload its remote configuration to compare with the local one. These requests ignored thecompliance_regionfield in the Wrangler configuration file and only honoured theCLOUDFLARE_COMPLIANCE_REGIONenvironment variable. A FedRAMP High Worker configured through the config file would send them toapi.cloudflare.cominstead ofapi.fed.cloudflare.com, and the deploy would fail with authentication errors. They now use the same compliance region as the rest of the deploy.#16359
262021dThanks @tw4! - Stop--strictdeploys and version uploads from aborting when the API omits optional binding fieldsPreviously,
wrangler deploy --strictandwrangler versions upload --strictcould report a destructive change for an unchanged configuration, for example an R2 bucket in the default jurisdiction, because a field the API left out was compared as removed. Missing and unset optional fields are now treated as equal, so these commands proceed when the local configuration matches the deployed Worker.Updated dependencies [
3464abc,017bf9b]:miniflare@5.20261019.1-beta
Patch Changes
#15708
3464abcThanks @samstarling! - Dispose Workflow step results and introspection modifiers after useRelease RPC resources deterministically during local Workflow execution and introspection. This prevents undisposed RPC warnings and requests being cancelled after their execution context has ended. Live step results retain their original data shape, including typed-array offsets and backing buffers. Callbacks that finish after a step times out also release their results, cancelling unused streams without delaying retries.
Disposing an introspector still aborts the instance if modifier acquisition failed, without introducing a teardown error. Non-stream results containing function-valued array properties are rejected according to the serialisable-output contract, instead of silently discarding those properties during storage normalisation.
@cloudflare/pages-shared@0.13.200
Patch Changes
3464abc]:@cloudflare/runtime-types@0.1.14
Patch Changes
3464abc]:@cloudflare/vite-plugin@2.0.0-beta.v.3
Patch Changes
#15846
a88cac4Thanks @oddharsh! - Fail with an error instead of hanging when local dev requests can't work under BunBun's
fetch()ignores the undicidispatcherthat Miniflare routes requests through (undici shim:Poollacksdispatch()/close()/destroy(), breaking miniflare + workerd (wrangler dev, @cloudflare/vite-plugin) oven-sh/bun#39247). Under Bun,createTestHarness()'sserver.fetch()andserver.getWorker()'sfetch(),email()andscheduled()now throw aUserError, requests to the dev server URL get a 503 naming the cause, and starting remote bindings throws aUserError. Each of these used to hang with no error.server.getWorker().getEnv()andgetExport()keep working under Bun.#16318
ff1f971Thanks @jamesopstad! - Prevent legacy Wrangler configuration files from being silently ignoredThe Vite plugin now stops with an actionable error when
wrangler.json,wrangler.jsonc, orwrangler.tomlis present withoutcloudflare.config.ts. Runnpx cf migrate --bundler viteto migrate the project before building.Updated dependencies [
3464abc]:@cloudflare/vitest-plugin@1.4.6
Patch Changes
#15708
3464abcThanks @samstarling! - Dispose Workflow step results and introspection modifiers after useRelease RPC resources deterministically during local Workflow execution and introspection. This prevents undisposed RPC warnings and requests being cancelled after their execution context has ended. Live step results retain their original data shape, including typed-array offsets and backing buffers. Callbacks that finish after a step times out also release their results, cancelling unused streams without delaying retries.
Disposing an introspector still aborts the instance if modifier acquisition failed, without introducing a teardown error. Non-stream results containing function-valued array properties are rejected according to the serialisable-output contract, instead of silently discarding those properties during storage normalisation.
#15846
a88cac4Thanks @oddharsh! - Fail with an error instead of hanging when local dev requests can't work under BunBun's
fetch()ignores the undicidispatcherthat Miniflare routes requests through (undici shim:Poollacksdispatch()/close()/destroy(), breaking miniflare + workerd (wrangler dev, @cloudflare/vite-plugin) oven-sh/bun#39247). Under Bun,createTestHarness()'sserver.fetch()andserver.getWorker()'sfetch(),email()andscheduled()now throw aUserError, requests to the dev server URL get a 503 naming the cause, and starting remote bindings throws aUserError. Each of these used to hang with no error.server.getWorker().getEnv()andgetExport()keep working under Bun.Updated dependencies [
4508172,61fc739,3464abc,a88cac4,262021d]:@cloudflare/workers-auth@0.14.1
Patch Changes
#16259
017bf9bThanks @NuroDev! - Support Vitest 5 in shared test helpersThe optional Vitest peer ranges now accept both Vitest 4 and 5, allowing consumers to upgrade without dropping compatibility with Vitest 4.
Updated dependencies [
017bf9b]:@cloudflare/workers-utils@0.47.3
Patch Changes
#16259
017bf9bThanks @NuroDev! - Support Vitest 5 in shared test helpersThe optional Vitest peer ranges now accept both Vitest 4 and 5, allowing consumers to upgrade without dropping compatibility with Vitest 4.
wrangler@4.151.3
Patch Changes
#15611
4508172Thanks @taylorlee! - Allowwrangler devto start module Workers without a default exportPreviously,
wrangler devfailed to start module Workers that exported only named entrypoints, such as RPC services, unless an unused default export was added. These Workers now start normally in local development without that workaround.#16370
61fc739Thanks @WalshyDev! - Fetch the remote config diff from the configured compliance regionWhen a Worker was last deployed from the dashboard,
wrangler deployandwrangler versions uploaddownload its remote configuration to compare with the local one. These requests ignored thecompliance_regionfield in the Wrangler configuration file and only honoured theCLOUDFLARE_COMPLIANCE_REGIONenvironment variable. A FedRAMP High Worker configured through the config file would send them toapi.cloudflare.cominstead ofapi.fed.cloudflare.com, and the deploy would fail with authentication errors. They now use the same compliance region as the rest of the deploy.#15846
a88cac4Thanks @oddharsh! - Fail with an error instead of hanging when local dev requests can't work under BunBun's
fetch()ignores the undicidispatcherthat Miniflare routes requests through (undici shim:Poollacksdispatch()/close()/destroy(), breaking miniflare + workerd (wrangler dev, @cloudflare/vite-plugin) oven-sh/bun#39247). Under Bun,createTestHarness()'sserver.fetch()andserver.getWorker()'sfetch(),email()andscheduled()now throw aUserError, requests to the dev server URL get a 503 naming the cause, and starting remote bindings throws aUserError. Each of these used to hang with no error.server.getWorker().getEnv()andgetExport()keep working under Bun.#16359
262021dThanks @tw4! - Stop--strictdeploys and version uploads from aborting when the API omits optional binding fieldsPreviously,
wrangler deploy --strictandwrangler versions upload --strictcould report a destructive change for an unchanged configuration, for example an R2 bucket in the default jurisdiction, because a field the API left out was compared as removed. Missing and unset optional fields are now treated as equal, so these commands proceed when the local configuration matches the deployed Worker.Updated dependencies [
3464abc]:@cloudflare/remote-bindings@0.0.51
Patch Changes
61fc739,3464abc,262021d,017bf9b]:@cloudflare/workers-playground@0.4.5
Patch Changes
#16323
3fa1e33Thanks @jamesopstad! - Migrate Workers Playground to use@cloudflare/vite-pluginv2 beta andcfA single
cloudflare.config.tsfile is now used for development and builds.cfis used in place of Wrangler for deployments.@cloudflare/workflows-shared@0.15.2
Patch Changes
#15708
3464abcThanks @samstarling! - Dispose Workflow step results and introspection modifiers after useRelease RPC resources deterministically during local Workflow execution and introspection. This prevents undisposed RPC warnings and requests being cancelled after their execution context has ended. Live step results retain their original data shape, including typed-array offsets and backing buffers. Callbacks that finish after a step times out also release their results, cancelling unused streams without delaying retries.
Disposing an introspector still aborts the instance if modifier acquisition failed, without introducing a teardown error. Non-stream results containing function-valued array properties are rejected according to the serialisable-output contract, instead of silently discarding those properties during storage normalisation.