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
[email protected]
Minor Changes
#9330
34c71ceThanks @edmundhung! - Add a newdefaultPersistRootoption to control where plugins persist data when no path is provided.Patch Changes
#9184
f7c82a4Thanks @dependabot! - chore: update dependencies of "miniflare" packageThe following dependency versions have been updated:
#9346
7ddd865Thanks @dependabot! - chore: update dependencies of "miniflare" packageThe following dependency versions have been updated:
#9335

6479fc5Thanks @penalosa! - Redesignwrangler devto more clearly present information and have a bit of a glow up ✨#9106
e5ae13aThanks @edmundhung! - fix: decouple KV plugin from secrets store pluginThe KV plugin previously configured both KV namespace and secrets store bindings with the same service name but different persistence paths, causing conflicts when both were defined. This change copies the KV binding implementation into the secrets store plugin and customizes its service name to prevent collisions.
@cloudflare/[email protected]
Minor Changes
34c71ceThanks @edmundhung! - Updated internal configuration to use Miniflare’s newdefaultPersistRootinstead of per-pluginpersistflagsPatch Changes
34c71ce,f7c82a4,7ddd865,6479fc5,410d985,e5ae13a,6c03bde,c2678d1,34c71ce,cc7fae4]:[email protected]
Minor Changes
#9321
6c03bdeThanks @petebacondarwin! - Add support for FedRAMP High compliance regionNow it is possible to target Wrangler at the FedRAMP High compliance region.
There are two ways to signal to Wrangler to run in this mode:
"compliance_region": "fedramp_high"in a Wrangler configurationCLOUDFLARE_COMPLIANCE_REGION=fedramp_highenvironment variable when running WranglerIf both are provided and the values do not match then Wrangler will exit with an error.
When in this mode OAuth authentication is not supported.
It is necessary to authenticate using a Cloudflare API Token acquired from the Cloudflare FedRAMP High dashboard.
Most bindings and commands are supported in this mode.
Resolves DEVX-1921.
#9330
34c71ceThanks @edmundhung! - Updated internal configuration to use Miniflare’s newdefaultPersistRootinstead of per-pluginpersistflags#8973
cc7fae4Thanks @Caio-Nogueira! - Show latest instance by default onworkflows instances describecommandPatch Changes
#9335

6479fc5Thanks @penalosa! - Redesignwrangler devto more clearly present information and have a bit of a glow up ✨#9329
410d985Thanks @penalosa! - Hide logs in thestartMixedModeSession()API#9325
c2678d1Thanks @edmundhung! - refactor: fallbacks to local image binding from miniflare when local mode is enabledUpdated dependencies [
34c71ce,f7c82a4,7ddd865,6479fc5,e5ae13a]:[email protected]
Patch Changes
a3496bfThanks @petebacondarwin! - add extra information about asset serving to hello-world templates@cloudflare/[email protected]
Patch Changes
34c71ce,f7c82a4,7ddd865,6479fc5,e5ae13a]:@cloudflare/[email protected]
Patch Changes
#9331
3c770ecThanks @petebacondarwin! - fix the Vitest integration to support Workers that want Node.js compatibility is only v1 in productionIt does this by adding the
nodejs_compat_v2flag (if missing) and removingno_nodejs_compat_v2flag (if found).This does mean that the Vitest tests are running with a slightly different environment to production, but this has always been the case in other ways.
#9350
68a9008Thanks @penalosa! - Don't crash Vitest when started with a non-existent tail consumerUpdated dependencies [
34c71ce,f7c82a4,7ddd865,6479fc5,410d985,e5ae13a,6c03bde,c2678d1,34c71ce,cc7fae4]: