wrangler@4.104.0
Minor Changes
-
#14369
e312decThanks @edmundhung! - AddgetEnv()tocreateTestHarness()Worker handlesTests can now access the full
envobject for a Worker withawait server.getWorker<Env>().getEnv(), including vars, secrets, and bindings.
Patch Changes
-
#14364
a085decThanks @dependabot! - Update dependencies of "miniflare", "wrangler"The following dependency versions have been updated:
Dependency From To workerd 1.20260617.1 1.20260619.1 -
#14383
9a0de8fThanks @dependabot! - Update dependencies of "miniflare", "wrangler"The following dependency versions have been updated:
Dependency From To workerd 1.20260619.1 1.20260621.1 -
#14397
fab565fThanks @dependabot! - Update dependencies of "miniflare", "wrangler"The following dependency versions have been updated:
Dependency From To workerd 1.20260621.1 1.20260623.1 -
#14388
3f02864Thanks @petebacondarwin! - Stop erroring whenfind_additional_modulesdiscovers a file that only matches a inactive module ruleModule rules assign module types to imported files — they are not include/exclude filters. Also, setting
fallthrough: falsein a rule will cause subsequent rules to become inactive. Previously, whenfind_additional_moduleswalked the filesystem and discovered a file whose only matching rule is inactive, Wrangler would throw an error and fail the build.This meant that adding a user rule like the one below would break the build for any
.txt,.html,.sql,.binor.wasmfile that didn't match the user-supplied globs but lived somewhere under the module root:Discovered files that only match an inactive rule are now silently skipped (a
debug-level log records each skip for troubleshooting), so users can usefallthrough: falseto narrow the set of files attached to their Worker without having to delete or move untouched files on disk.The direct-import path is unchanged: importing a file in code that only matches an inactive rule is still a hard error, because the imported file genuinely needs a defined module type.
Fixes #14257.
-
#14358
4ef872fThanks @gabivlj! - Fix container egress interception on arm64 Docker runtimesBoth
wrangler devand the Cloudflare Vite plugin no longer force theproxy-everythingsidecar image to pull aslinux/amd64, allowing Docker to select the native image from the multi-platform manifest. SetMINIFLARE_CONTAINER_EGRESS_IMAGE_PLATFORMto force a specific platform when needed. -
#14362
2a02858Thanks @sherryliu-lsy! - Don't require the private credential when reusing an existing Secrets Store secret incontainers registries configurewrangler containers registries configurenow checks whether the target Secrets Store secret already exists before resolving the private credential. When the secret already exists it is reused by reference, so the private credential no longer needs to be supplied (via stdin in non-interactive mode, or via a prompt interactively). This applies to all external registries.The new-secret path is unchanged: the credential is still required and stored. The only visible interactive change is that the secret prompt now appears last and only when a new secret is being created.
-
Updated dependencies [
a085dec,9a0de8f,fab565f]:- miniflare@4.20260623.0