chore(deps): update dependency wrangler to v4.70.0#1085
Merged
Conversation
Deploying somehow-digital-website with
|
| Latest commit: |
cbd199a
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://27a60947.somehow-digital-website.pages.dev |
| Branch Preview URL: | https://renovate-wrangler-4-x-lockfi.somehow-digital-website.pages.dev |
7630fe0 to
4bfe071
Compare
4bfe071 to
7724f3f
Compare
7724f3f to
d6bbba7
Compare
d6bbba7 to
9ba276c
Compare
9ba276c to
8d0f080
Compare
ddbb9c4 to
173793d
Compare
173793d to
cbd199a
Compare
|
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 contains the following updates:
4.65.0→4.70.0Release Notes
cloudflare/workers-sdk (wrangler)
v4.70.0Compare Source
Minor Changes
#11332
6a8aa5fThanks @nikitassharma! - Users are now able to configure DockerHub credentials and have containers reference images stored there.DockerHub can be configured as follows:
Containers can then specify an image from DockerHub in their
wrangler.jsoncas follows:#12649
35b2c56Thanks @gabivlj! - Add experimental support for containers to workers communication with interceptOutboundHttpThis feature is experimental and requires adding the "experimental" compatibility flag to your Wrangler configuration.
#12701
23a365aThanks @jamesopstad! - Add local dev validation for the experimentalsecretsconfiguration propertyWhen the new
secretsproperty is defined,wrangler devandvite devnow validate secrets declared insecrets.required. When required secrets are missing from.dev.varsor.env/process.env, a warning is logged listing the missing secret names.When
secretsis defined, only the keys listed insecrets.requiredare loaded. Additional keys in.dev.varsor.envare excluded. If you are not using.dev.vars, keys listed insecrets.requiredare loaded fromprocess.envas well as.env. TheCLOUDFLARE_INCLUDE_PROCESS_ENVenvironment variable is therefore not needed when using this feature.When
secretsis not defined, the existing behavior is unchanged.#12695
0769056Thanks @jamesopstad! - Add type generation for the experimentalsecretsconfiguration propertyWhen the new
secretsproperty is defined,wrangler typesnow generates typed bindings from the names listed insecrets.required.When
secretsis defined at any config level, type generation uses it exclusively and no longer infers secret names from.dev.varsor.envfiles. This enables running type generation in environments where these files are not present.Per-environment secrets are supported. Each named environment produces its own interface, and the aggregated
Envmarks secrets that only appear in some environments as optional.When
secretsis not defined, the existing behavior is unchanged.#12693
150ef7bThanks @martinezjandrew! - Addwrangler containers registries credentialscommand for generating temporary push/pull credentialsThis command generates short-lived credentials for authenticating with the Cloudflare managed registry (
registry.cloudflare.com). Useful for CI/CD pipelines or local Docker authentication.#12622
bf9cb3dThanks @LuisDuarte1! - Add configurable step limits for WorkflowsYou can now set a maximum number of steps for a Workflow instance via the
limits.stepsconfiguration in your Wrangler config. When a Workflow instance exceeds this limit, it will fail with an error indicating the limit was reached.The
stepsvalue must be an integer between 1 and 25,000. If not specified, the default limit of 10,000 steps is used. Step limits are also enforced in local development viawrangler dev.Patch Changes
#12733
d672e2eThanks @dario-piotrowicz! - Fix SolidStart autoconfig for projects using version 2.0.0-alpha or laterSolidStart v2.0.0-alpha introduced a breaking change where configuration moved from
app.config.(js|ts)tovite.config.(js|ts). Wrangler's autoconfig now detects the installed SolidStart version and based on it updates the appropriate configuration file#12698
209b396Thanks @penalosa! - Update dependencies of "miniflare", "wrangler"The following dependency versions have been updated:
#12691
596b8a0Thanks @penalosa! - Remove temporary AI Search RPC workaround (no user-facing changes)#12694
00e729eThanks @garvit-gupta! - Fixwrangler pipelines setupfailing for Data Catalog sinks on new buckets by using the correct R2 Catalog API error code (40401).Updated dependencies [
35b2c56,5f7aaf2,209b396,596b8a0,bf9cb3d]:v4.69.0Compare Source
Minor Changes
#12625
c0e9e08Thanks @WillTaylorDev! - Addcacheconfiguration option for enabling worker cache (experimental)You can now enable cache before worker execution using the new
cacheconfiguration:{ "cache": { "enabled": true, }, }This setting is environment-inheritable and opt-in. When enabled, cache behavior is applied before your worker runs.
Note: This feature is experimental. The runtime API is not yet generally available.
Patch Changes
#12661
99037e3Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"The following dependency versions have been updated:
#12680
295297aThanks @dependabot! - Update dependencies of "miniflare", "wrangler"The following dependency versions have been updated:
#12671
f765244Thanks @MattieTK! - fix: Only redact account names in CI environments, not all non-interactive contextsThe multi-account selection error in
getAccountIdnow only redacts account nameswhen running in a CI environment (detected via
ci-info). Non-interactive terminalssuch as coding agents and piped commands can now see account names, which they need
to identify which account to configure. CI logs remain protected.
Updated dependencies [
99037e3,295297a]:v4.68.1Compare Source
Patch Changes
#12648
3d6e421Thanks @petebacondarwin! - Fix Angular scaffolding to allow localhost SSR in development modeRecent versions of Angular's
AngularAppEngineblock serving SSR onlocalhostby default. This causedwrangler dev/wrangler pages devto fail withURL with hostname "localhost" is not allowed.The fix passes
allowedHosts: ["localhost"]to theAngularAppEngineconstructor inserver.ts, which is safe to do even in production since Cloudflare will already restrict which host is allowed.#12657
294297eThanks @dario-piotrowicz! - Update Waku autoconfig logicAs of
1.0.0-alpha.4, Waku projects can be built on top of the Cloudflare Vite plugin, and the changes here allow Wrangler autoconfig to support this. Running autoconfig on older versions of Waku will result in an error.Updated dependencies []:
v4.68.0Compare Source
Minor Changes
#12614
8d882faThanks @dario-piotrowicz! - Enable autoconfig forwrangler deployby default (while allowing users to still disable it via--x-autoconfig=falseif necessary)#12614
8d882faThanks @dario-piotrowicz! - Mark thewrangler setupcommand as stablev4.67.1Compare Source
Patch Changes
#12595
e93dc01Thanks @dario-piotrowicz! - Add a warning in the autoconfig logic letting users know that support for projects inside workspaces is limited#12582
c2ed7c2Thanks @penalosa! - Internal refactor to use capnweb's nativeReadableStreamsupport to power remote Media and Dispatch Namespace bindings.#12618
d920811Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"The following dependency versions have been updated:
#12637
896734dThanks @dependabot! - Update dependencies of "miniflare", "wrangler"The following dependency versions have been updated:
#12601
ebdbe52Thanks @43081j! - Switch toempathicfor file-system upwards traversal to reduce dependency bloat.#12602
58a4020Thanks @anonrig! - Optimize filesystem operations by using Node.js's throwIfNoEntry: false optionThis reduces the number of system calls made when checking for file existence by avoiding the overhead of throwing and catching errors for missing paths. This is an internal performance optimization with no user-visible behavioral changes.
#12591
6f6cd94Thanks @martinezjandrew! - Implemented logic withinwrangler containers registries configureto check if a specified secret name is already in-use and offer to reuse that secret. Also added--skip-confirmationflag to the command to skip all interactive prompts.Updated dependencies [
c2ed7c2,d920811,896734d,58a4020]:v4.67.0Compare Source
Minor Changes
#12401
8723684Thanks @jonesphillip! - Add validation retry loops to pipelines setup commandThe
wrangler pipelines setupcommand now prompts users to retry when validation errors occur, instead of failing the entire setup process. This includes:This improves the setup experience by allowing users to correct mistakes without restarting the entire configuration flow.
#12395
aa82c2bThanks @cmackenzie1! - Generate typed pipeline bindings from stream schemasWhen running
wrangler types, pipeline bindings now generate TypeScript types based on the stream's schema definition. This gives you full autocomplete and type checking when sending data to your pipelines.If your stream has a schema with fields like
user_id(string) andevent_count(int32), the generated types will be:For unstructured streams or when not authenticated, bindings fall back to the generic
Pipeline<PipelineRecord>type.Patch Changes
#12592
aaa7200Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"The following dependency versions have been updated:
#12606
2f19a40Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"The following dependency versions have been updated:
#12604
e2a6600Thanks @petebacondarwin! - fix: pass--envflag to auxiliary workers in multi-worker modeWhen running
wrangler devwith multiple config files (e.g.-c ./apps/api/wrangler.jsonc -c ./apps/queues/wrangler.jsonc -e=dev), the--envflag was not being passed to auxiliary (non-primary) workers. This meant that environment-specific configuration (such as queue bindings) was not applied to auxiliary workers, causing features like queue consumers to not be triggered in local development.#12597
0b17117Thanks @sdnts! - The maximum allowed delivery and retry delays for Queues is now 24 hours#12598
ca58062Thanks @mattzcarey! - Stop redactingwrangler whoamioutput in non-interactive modewrangler whoamiis explicitly invoked to retrieve account info, so email and account names should always be visible. Redacting them in non-interactive/CI environments makes it difficult for coding agents and automated tools to identify which account to use. Other error messages that may appear unexpectedly in CI logs (e.g. multi-account selection errors) remain redacted.Updated dependencies [
f239077,aaa7200,2f19a40,5f9f0b4,452cdc8,527e4f5,0b17117]:v4.66.0Compare Source
Minor Changes
#12466
caf9b11Thanks @petebacondarwin! - AddWRANGLER_CACHE_DIRenvironment variable and smart cache directory detectionWrangler now intelligently detects where to store cache files:
WRANGLER_CACHE_DIRenv var if setnode_modules/.cache/wrangleror.wrangler/cache)node_modules/.cache/wranglerifnode_modulesexists.wrangler/cacheThis improves compatibility with Yarn PnP, pnpm, and other package managers that don't use traditional
node_modulesdirectories, without requiring any configuration.#12572
936187dThanks @dario-piotrowicz! - Ensure thenodejs_compatflag is always applied in autoconfigPreviously, the autoconfig feature relied on individual framework configurations to specify Node.js compatibility flags, some could set
nodejs_compatwhile othersnodejs_als.Now instead
nodejs_compatis always included as a compatibility flag, this is generally beneficial and the user can always remove the flag afterwards if they want to.#12560
c4c86f8Thanks @taylorlee! - Support--tagand--messageflags onwrangler deployThey have the same behavior that they do as during
wrangler versions upload, as bothare set on the version.
The message is also reused for the deployment as well, with the same behavior as used
during
wrangler versions deploy.Patch Changes
#12543
5a868a0Thanks @G4brym! - Fix AI Search binding failing in local devUsing AI Search bindings with
wrangler devwould fail with "RPC stub points at a non-serializable type". AI Search bindings now work correctly in local development.#12552
c58e81bThanks @dependabot! - Update dependencies of "miniflare", "wrangler"The following dependency versions have been updated:
#12568
33a9a8fThanks @dependabot! - Update dependencies of "miniflare", "wrangler"The following dependency versions have been updated:
#12576
8077c14Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"The following dependency versions have been updated:
#12466
caf9b11Thanks @petebacondarwin! - fix: exclude.wranglerdirectory from Pages uploadsThe
.wranglerdirectory contains local cache and state files that should never be deployed. This aligns Pages upload behavior with Workers Assets, which already excludes.wranglervia.assetsignore.#12556
7d2355eThanks @ascorbic! - Fix port availability check probing the wrong host when host changesmemoizeGetPortcorrectly invalidated its cached port when called with a different host, but then still probed the original host for port availability. This could return a port that was free on the original host but already in use on the requested one, leading to bind failures at startup.#12562
7ea69afThanks @MattieTK! - Support function-based Vite configs in autoconfig setupwrangler setupandwrangler deploy --x-autoconfigcan now automatically add the Cloudflare Vite plugin to projects that use function-baseddefineConfig()patterns. Previously, autoconfig would fail with "Cannot modify Vite config: expected an object literal but found ArrowFunctionExpression" for configs like:This pattern is used by several official framework templates, including React Router's
node-postgresandnode-custom-servertemplates. The followingdefineConfig()patterns are now supported:defineConfig({ ... })(object literal, already worked)defineConfig(() => ({ ... }))(arrow function with expression body)defineConfig(({ isSsrBuild }) => ({ ... }))(arrow function with destructured params)defineConfig(() => { return { ... }; })(arrow function with block body)defineConfig(function() { return { ... }; })(function expression)#12548
5cc7158Thanks @dario-piotrowicz! - Fix.assetsignoreformatting when autoconfig creates a new filePreviously, when
wrangler setuporwrangler deploy --x-autoconfigcreated a new.assetsignorefile via autoconfig, it would add unnecessary leading empty lines before the wrangler-specific entries. Empty separator lines should only be added when appending to an existing.assetsignorefile. This fix ensures newly created.assetsignorefiles start cleanly without leading blank lines.#12556
7d2355eThanks @ascorbic! - Improve error message when port binding is blocked by a sandbox or security policyWhen running
wrangler devinside a restricted environment (such as an AI coding agent sandbox or locked-down container), the port availability check would fail with a rawEPERMerror. This now provides a clear message explaining that a sandbox or security policy is blocking network access, rather than the generic permission error that previously pointed at the file system.#12545
c9d0f9dThanks @dario-piotrowicz! - Improve framework detection when multiple frameworks are foundWhen autoconfig detects multiple frameworks in a project, Wrangler now applies smarter logic to select the most appropriate one. Selecting the wrong one is acceptable locally where the user can change the detected framework, in CI an error is instead thrown.
#12548
5cc7158Thanks @dario-piotrowicz! - Add trailing newline to generatedpackage.jsonandwrangler.jsoncfiles#12548
5cc7158Thanks @dario-piotrowicz! - Fix.gitignoreformatting when autoconfig creates a new filePreviously, when
wrangler setuporwrangler deploycreated a new.gitignorefile via autoconfig, it would add unnecessary leading empty lines before the wrangler-specific entries. Empty separator lines should only be added when appending to an existing.gitignorefile. This fix ensures newly created.gitignorefiles start cleanly without leading blank lines.#12545
c9d0f9dThanks @dario-piotrowicz! - Throw actionable error when autoconfig is run in the root of a workspaceWhen running Wrangler commands that trigger auto-configuration (like
wrangler devorwrangler deploy) in the root directory of a monorepo workspace, a helpful error is now shown directing users to run the command in a specific project's directory instead.Updated dependencies [
5a868a0,c58e81b,33a9a8f,8077c14,caf9b11,9a565d5,7f18183,39491f9,43c462a]:Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.