Skip to content

chore(deps): update dependency wrangler to v4.70.0#1085

Merged
thasmo merged 1 commit intomainfrom
renovate/wrangler-4.x-lockfile
Mar 4, 2026
Merged

chore(deps): update dependency wrangler to v4.70.0#1085
thasmo merged 1 commit intomainfrom
renovate/wrangler-4.x-lockfile

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Feb 17, 2026

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
wrangler (source) 4.65.04.70.0 age adoption passing confidence

Release Notes

cloudflare/workers-sdk (wrangler)

v4.70.0

Compare Source

Minor Changes
  • #​11332 6a8aa5f Thanks @​nikitassharma! - Users are now able to configure DockerHub credentials and have containers reference images stored there.

    DockerHub can be configured as follows:

    echo $PAT_TOKEN | npx wrangler@latest containers registries configure docker.io --dockerhub-username=user --secret-name=DockerHub_PAT_Token

    Containers can then specify an image from DockerHub in their wrangler.jsonc as follows:

    "containers": {
      "image": "docker.io/namespace/image:tag",
      ...
    }
  • #​12649 35b2c56 Thanks @​gabivlj! - Add experimental support for containers to workers communication with interceptOutboundHttp

    This feature is experimental and requires adding the "experimental" compatibility flag to your Wrangler configuration.

  • #​12701 23a365a Thanks @​jamesopstad! - Add local dev validation for the experimental secrets configuration property

    When the new secrets property is defined, wrangler dev and vite dev now validate secrets declared in secrets.required. When required secrets are missing from .dev.vars or .env/process.env, a warning is logged listing the missing secret names.

    When secrets is defined, only the keys listed in secrets.required are loaded. Additional keys in .dev.vars or .env are excluded. If you are not using .dev.vars, keys listed in secrets.required are loaded from process.env as well as .env. The CLOUDFLARE_INCLUDE_PROCESS_ENV environment variable is therefore not needed when using this feature.

    When secrets is not defined, the existing behavior is unchanged.

    // wrangler.jsonc
    {
    	"secrets": {
    		"required": ["API_KEY", "DB_PASSWORD"],
    	},
    }
  • #​12695 0769056 Thanks @​jamesopstad! - Add type generation for the experimental secrets configuration property

    When the new secrets property is defined, wrangler types now generates typed bindings from the names listed in secrets.required.

    When secrets is defined at any config level, type generation uses it exclusively and no longer infers secret names from .dev.vars or .env files. 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 Env marks secrets that only appear in some environments as optional.

    When secrets is not defined, the existing behavior is unchanged.

    // wrangler.jsonc
    {
    	"secrets": {
    		"required": ["API_KEY", "DB_PASSWORD"],
    	},
    }
  • #​12693 150ef7b Thanks @​martinezjandrew! - Add wrangler containers registries credentials command for generating temporary push/pull credentials

    This command generates short-lived credentials for authenticating with the Cloudflare managed registry (registry.cloudflare.com). Useful for CI/CD pipelines or local Docker authentication.

    # Generate push credentials (for uploading images)
    wrangler containers registries credentials registry.cloudflare.com --push
    
    # Generate pull credentials (for downloading images)
    wrangler containers registries credentials registry.cloudflare.com --pull
    
    # Generate credentials with both permissions
    wrangler containers registries credentials registry.cloudflare.com --push --pull
    
    # Custom expiration (default 15)
    wrangler containers registries credentials registry.cloudflare.com --push --expiration-minutes=30
  • #​12622 bf9cb3d Thanks @​LuisDuarte1! - Add configurable step limits for Workflows

    You can now set a maximum number of steps for a Workflow instance via the limits.steps configuration in your Wrangler config. When a Workflow instance exceeds this limit, it will fail with an error indicating the limit was reached.

    // wrangler.jsonc
    {
    	"workflows": [
    		{
    			"binding": "MY_WORKFLOW",
    			"name": "my-workflow",
    			"class_name": "MyWorkflow",
    			"limits": {
    				"steps": 5000,
    			},
    		},
    	],
    }

    The steps value 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 via wrangler dev.

Patch Changes
  • #​12733 d672e2e Thanks @​dario-piotrowicz! - Fix SolidStart autoconfig for projects using version 2.0.0-alpha or later

    SolidStart v2.0.0-alpha introduced a breaking change where configuration moved from app.config.(js|ts) to vite.config.(js|ts). Wrangler's autoconfig now detects the installed SolidStart version and based on it updates the appropriate configuration file

  • #​12698 209b396 Thanks @​penalosa! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    workerd 1.20260305.0 1.20260226.1
    @​cloudflare/workers-types 4.20260305.0 4.20260226.1
  • #​12691 596b8a0 Thanks @​penalosa! - Remove temporary AI Search RPC workaround (no user-facing changes)

  • #​12694 00e729e Thanks @​garvit-gupta! - Fix wrangler pipelines setup failing for Data Catalog sinks on new buckets by using the correct R2 Catalog API error code (40401).

  • Updated dependencies [35b2c56, 5f7aaf2, 209b396, 596b8a0, bf9cb3d]:

    • miniflare@​4.20260301.1

v4.69.0

Compare Source

Minor Changes
  • #​12625 c0e9e08 Thanks @​WillTaylorDev! - Add cache configuration option for enabling worker cache (experimental)

    You can now enable cache before worker execution using the new cache configuration:

    {
    	"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 99037e3 Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    workerd 1.20260302.0 1.20260303.0
  • #​12680 295297a Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    workerd 1.20260303.0 1.20260305.0
  • #​12671 f765244 Thanks @​MattieTK! - fix: Only redact account names in CI environments, not all non-interactive contexts

    The multi-account selection error in getAccountId now only redacts account names
    when running in a CI environment (detected via ci-info). Non-interactive terminals
    such 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]:

    • miniflare@​4.20260305.0

v4.68.1

Compare Source

Patch Changes
  • #​12648 3d6e421 Thanks @​petebacondarwin! - Fix Angular scaffolding to allow localhost SSR in development mode

    Recent versions of Angular's AngularAppEngine block serving SSR on localhost by default. This caused wrangler dev / wrangler pages dev to fail with URL with hostname "localhost" is not allowed.

    The fix passes allowedHosts: ["localhost"] to the AngularAppEngine constructor in server.ts, which is safe to do even in production since Cloudflare will already restrict which host is allowed.

  • #​12657 294297e Thanks @​dario-piotrowicz! - Update Waku autoconfig logic

    As 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 []:

    • miniflare@​4.20260302.0

v4.68.0

Compare Source

Minor Changes

v4.67.1

Compare Source

Patch Changes
  • #​12595 e93dc01 Thanks @​dario-piotrowicz! - Add a warning in the autoconfig logic letting users know that support for projects inside workspaces is limited

  • #​12582 c2ed7c2 Thanks @​penalosa! - Internal refactor to use capnweb's native ReadableStream support to power remote Media and Dispatch Namespace bindings.

  • #​12618 d920811 Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    workerd 1.20260219.0 1.20260227.0
  • #​12637 896734d Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    workerd 1.20260227.0 1.20260302.0
  • #​12601 ebdbe52 Thanks @​43081j! - Switch to empathic for file-system upwards traversal to reduce dependency bloat.

  • #​12602 58a4020 Thanks @​anonrig! - Optimize filesystem operations by using Node.js's throwIfNoEntry: false option

    This 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 6f6cd94 Thanks @​martinezjandrew! - Implemented logic within wrangler containers registries configure to check if a specified secret name is already in-use and offer to reuse that secret. Also added --skip-confirmation flag to the command to skip all interactive prompts.

  • Updated dependencies [c2ed7c2, d920811, 896734d, 58a4020]:

    • miniflare@​4.20260302.0

v4.67.0

Compare Source

Minor Changes
  • #​12401 8723684 Thanks @​jonesphillip! - Add validation retry loops to pipelines setup command

    The wrangler pipelines setup command now prompts users to retry when validation errors occur, instead of failing the entire setup process. This includes:

    • Validation retry prompts for pipeline names, bucket names, and field names
    • A "simple" mode for sink configuration that uses sensible defaults
    • Automatic bucket creation when buckets don't exist
    • Automatic Data Catalog enablement when not already active

    This improves the setup experience by allowing users to correct mistakes without restarting the entire configuration flow.

  • #​12395 aa82c2b Thanks @​cmackenzie1! - Generate typed pipeline bindings from stream schemas

    When 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.

    // wrangler.json
    {
    	"pipelines": [
    		{ "binding": "ANALYTICS", "pipeline": "analytics-stream-id" },
    	],
    }

    If your stream has a schema with fields like user_id (string) and event_count (int32), the generated types will be:

    declare namespace Cloudflare {
    	type AnalyticsStreamRecord = { user_id: string; event_count: number };
    	interface Env {
    		ANALYTICS: Pipeline<Cloudflare.AnalyticsStreamRecord>;
    	}
    }

    For unstructured streams or when not authenticated, bindings fall back to the generic Pipeline<PipelineRecord> type.

Patch Changes
  • #​12592 aaa7200 Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    workerd 1.20260217.0 1.20260218.0
  • #​12606 2f19a40 Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    workerd 1.20260218.0 1.20260219.0
  • #​12604 e2a6600 Thanks @​petebacondarwin! - fix: pass --env flag to auxiliary workers in multi-worker mode

    When running wrangler dev with multiple config files (e.g. -c ./apps/api/wrangler.jsonc -c ./apps/queues/wrangler.jsonc -e=dev), the --env flag 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 0b17117 Thanks @​sdnts! - The maximum allowed delivery and retry delays for Queues is now 24 hours

  • #​12598 ca58062 Thanks @​mattzcarey! - Stop redacting wrangler whoami output in non-interactive mode

    wrangler whoami is 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.0

Compare Source

Minor Changes
  • #​12466 caf9b11 Thanks @​petebacondarwin! - Add WRANGLER_CACHE_DIR environment variable and smart cache directory detection

    Wrangler now intelligently detects where to store cache files:

    1. Use WRANGLER_CACHE_DIR env var if set
    2. Use existing cache directory if found (node_modules/.cache/wrangler or .wrangler/cache)
    3. Create cache in node_modules/.cache/wrangler if node_modules exists
    4. Otherwise use .wrangler/cache

    This improves compatibility with Yarn PnP, pnpm, and other package managers that don't use traditional node_modules directories, without requiring any configuration.

  • #​12572 936187d Thanks @​dario-piotrowicz! - Ensure the nodejs_compat flag is always applied in autoconfig

    Previously, the autoconfig feature relied on individual framework configurations to specify Node.js compatibility flags, some could set nodejs_compat while others nodejs_als.

    Now instead nodejs_compat is always included as a compatibility flag, this is generally beneficial and the user can always remove the flag afterwards if they want to.

  • #​12560 c4c86f8 Thanks @​taylorlee! - Support --tag and --message flags on wrangler deploy

    They have the same behavior that they do as during wrangler versions upload, as both
    are 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 5a868a0 Thanks @​G4brym! - Fix AI Search binding failing in local dev

    Using AI Search bindings with wrangler dev would fail with "RPC stub points at a non-serializable type". AI Search bindings now work correctly in local development.

  • #​12552 c58e81b Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    workerd 1.20260212.0 1.20260213.0
  • #​12568 33a9a8f Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    workerd 1.20260213.0 1.20260214.0
  • #​12576 8077c14 Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    workerd 1.20260214.0 1.20260217.0
  • #​12466 caf9b11 Thanks @​petebacondarwin! - fix: exclude .wrangler directory from Pages uploads

    The .wrangler directory contains local cache and state files that should never be deployed. This aligns Pages upload behavior with Workers Assets, which already excludes .wrangler via .assetsignore.

  • #​12556 7d2355e Thanks @​ascorbic! - Fix port availability check probing the wrong host when host changes

    memoizeGetPort correctly 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 7ea69af Thanks @​MattieTK! - Support function-based Vite configs in autoconfig setup

    wrangler setup and wrangler deploy --x-autoconfig can now automatically add the Cloudflare Vite plugin to projects that use function-based defineConfig() patterns. Previously, autoconfig would fail with "Cannot modify Vite config: expected an object literal but found ArrowFunctionExpression" for configs like:

    export default defineConfig(({ isSsrBuild }) => ({
    	plugins: [reactRouter(), tsconfigPaths()],
    }));

    This pattern is used by several official framework templates, including React Router's node-postgres and node-custom-server templates. The following defineConfig() 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 5cc7158 Thanks @​dario-piotrowicz! - Fix .assetsignore formatting when autoconfig creates a new file

    Previously, when wrangler setup or wrangler deploy --x-autoconfig created a new .assetsignore file 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 .assetsignore file. This fix ensures newly created .assetsignore files start cleanly without leading blank lines.

  • #​12556 7d2355e Thanks @​ascorbic! - Improve error message when port binding is blocked by a sandbox or security policy

    When running wrangler dev inside a restricted environment (such as an AI coding agent sandbox or locked-down container), the port availability check would fail with a raw EPERM error. 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 c9d0f9d Thanks @​dario-piotrowicz! - Improve framework detection when multiple frameworks are found

    When 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 5cc7158 Thanks @​dario-piotrowicz! - Add trailing newline to generated package.json and wrangler.jsonc files

  • #​12548 5cc7158 Thanks @​dario-piotrowicz! - Fix .gitignore formatting when autoconfig creates a new file

    Previously, when wrangler setup or wrangler deploy created a new .gitignore file 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 .gitignore file. This fix ensures newly created .gitignore files start cleanly without leading blank lines.

  • #​12545 c9d0f9d Thanks @​dario-piotrowicz! - Throw actionable error when autoconfig is run in the root of a workspace

    When running Wrangler commands that trigger auto-configuration (like wrangler dev or wrangler 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot requested a review from thasmo as a code owner February 17, 2026 15:57
@cloudflare-workers-and-pages
Copy link
Copy Markdown

cloudflare-workers-and-pages Bot commented Feb 17, 2026

Deploying somehow-digital-website with  Cloudflare Pages  Cloudflare Pages

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

View logs

@renovate renovate Bot force-pushed the renovate/wrangler-4.x-lockfile branch from 7630fe0 to 4bfe071 Compare February 19, 2026 18:33
@renovate renovate Bot changed the title chore(deps): update dependency wrangler to v4.66.0 chore(deps): update dependency wrangler to v4.67.0 Feb 19, 2026
@renovate renovate Bot force-pushed the renovate/wrangler-4.x-lockfile branch from 4bfe071 to 7724f3f Compare February 23, 2026 22:07
@renovate renovate Bot changed the title chore(deps): update dependency wrangler to v4.67.0 chore(deps): update dependency wrangler to v4.68.0 Feb 23, 2026
@renovate renovate Bot force-pushed the renovate/wrangler-4.x-lockfile branch from 7724f3f to d6bbba7 Compare February 24, 2026 17:02
@renovate renovate Bot changed the title chore(deps): update dependency wrangler to v4.68.0 chore(deps): update dependency wrangler to v4.68.1 Feb 24, 2026
@renovate renovate Bot force-pushed the renovate/wrangler-4.x-lockfile branch from d6bbba7 to 9ba276c Compare February 26, 2026 16:51
@renovate renovate Bot changed the title chore(deps): update dependency wrangler to v4.68.1 chore(deps): update dependency wrangler to v4.69.0 Feb 26, 2026
@renovate renovate Bot force-pushed the renovate/wrangler-4.x-lockfile branch from 9ba276c to 8d0f080 Compare March 3, 2026 22:08
@renovate renovate Bot changed the title chore(deps): update dependency wrangler to v4.69.0 chore(deps): update dependency wrangler to v4.70.0 Mar 3, 2026
@renovate renovate Bot force-pushed the renovate/wrangler-4.x-lockfile branch 6 times, most recently from ddbb9c4 to 173793d Compare March 4, 2026 18:03
@renovate renovate Bot force-pushed the renovate/wrangler-4.x-lockfile branch from 173793d to cbd199a Compare March 4, 2026 18:17
@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud Bot commented Mar 4, 2026

@thasmo thasmo added this pull request to the merge queue Mar 4, 2026
Merged via the queue into main with commit ba029a7 Mar 4, 2026
5 checks passed
@thasmo thasmo deleted the renovate/wrangler-4.x-lockfile branch March 4, 2026 19:19
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