Update dependency wrangler to v4.70.0 by renovate[bot] · Pull Request #10 · BoomchainLabs/database

renovate · 2026-02-13T18:22:47Z

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
wrangler (source)	`4.59.1` → `4.70.0`

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

#12614 8d882fa Thanks @dario-piotrowicz! - Enable autoconfig for wrangler deploy by default (while allowing users to still disable it via --x-autoconfig=false if necessary)
#12614 8d882fa Thanks @dario-piotrowicz! - Mark the wrangler setup command as stable

`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]:
- miniflare@4.20260219.0
- @cloudflare/unenv-preset@2.14.0

`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]:
- miniflare@4.20260217.0
- @cloudflare/unenv-preset@2.13.0

`v4.65.0`

Compare Source

Minor Changes

#12473 b900c5a Thanks @petebacondarwin! - Add CF_PAGES environment variables to wrangler pages dev

wrangler pages dev now automatically injects Pages-specific environment variables (CF_PAGES, CF_PAGES_BRANCH, CF_PAGES_COMMIT_SHA, CF_PAGES_URL) for improved dev/prod parity. This enables frameworks like SvelteKit to auto-detect the Pages environment during local development.
- CF_PAGES is set to "1" to indicate the Pages environment
- CF_PAGES_BRANCH defaults to the current git branch (or "local" if not in a git repo)
- CF_PAGES_COMMIT_SHA defaults to the current git commit SHA (or a placeholder if not in a git repo)
- CF_PAGES_URL is set to a simulated commit preview URL (e.g., https://<sha>.<project-name>.pages.dev)
These variables are displayed with their actual values in the bindings table during startup, making it easy to verify what branch and commit SHA were detected.

These variables can be overridden by user-defined vars in the Wrangler configuration, .env, .dev.vars, or via CLI flags.
#12464 10a1c4a Thanks @petebacondarwin! - Allow deleting KV namespaces by name

You can now delete a KV namespace by providing its name as a positional argument:
```
wrangler kv namespace delete my-namespace
```
This aligns the delete command with the create command, which also accepts a namespace name.
The existing --namespace-id and --binding flags continue to work as before.
#12382 d7b492c Thanks @dario-piotrowicz! - Add Pages detection to autoconfig flows

When running the autoconfig logic (via wrangler setup, wrangler deploy --x-autoconfig, or the programmatic autoconfig API), Wrangler now detects when a project appears to be a Pages project and handles it appropriately:
- For wrangler deploy, it warns the user but still allows them to proceed
- For wrangler setup and the programmatic autoconfig API, it throws a fatal error
#12461 8809411 Thanks @penalosa! - Support type: inherit bindings when using startWorker()

This is an internal binding type that should not be used by external users of the API
#12515 1a9eddd Thanks @ascorbic! - Add --json flag to wrangler whoami for machine-readable output

wrangler whoami --json now outputs structured JSON containing authentication status, auth type, email, accounts, and token permissions. When the user is not authenticated, the command exits with a non-zero status code and outputs {"loggedIn":false}, making it easy to check auth status in shell scripts without parsing text output.
```
# Parse the JSON output
wrangler whoami --json | jq '.accounts'

# Check if authenticated in a script. Returns 0 if authenticated, non-zero if not.
if wrangler whoami --json > /dev/null 2>&1; then
  echo "Authenticated"
else
  echo "Not authenticated"
fi
```

Patch Changes

#12437 ad817dd Thanks @MattieTK! - fix: use project's package manager in wranger autoconfig

wrangler setup now correctly detects and uses the project's package manager based on lockfiles (pnpm-lock.yaml, yarn.lock, bun.lockb, package-lock.json) and the packageManager field in package.json. Previously, it would fall back to the package manager used to execute the command when run directly from the terminal, causing failures in pnpm and yarn workspace projects if the wrong manager was used in this step due to the workspace: protocol not being supported by npm.

This change leverages the package manager detection already performed by @netlify/build-info during framework detection, ensuring consistent behaviour across the autoconfig process.
#12541 f7fa326 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"

The following dependency versions have been updated:

Dependency From To

workerd 1.20260210.0 1.20260212.0
#12498 734792a Thanks @dario-piotrowicz! - Fix: make sure that remote proxy sessions's logs can be silenced when the wrangler log level is set to "none"
#12135 cc5ac22 Thanks @edmundhung! - Fix spurious config diffs when bindings from local and remote config are shown in different order

When comparing local and remote Worker configurations, binding arrays like kv_namespaces would incorrectly show additions and removals if the elements were in a different order. The diff now correctly recognizes these as equivalent by reordering remote arrays to match the local config's order before comparison.
#12476 62a8d48 Thanks @MattieTK! - fix: use unscoped binary name for OpenNext autoconfig command overrides

The build, deploy, and version command overrides in the Next.js (OpenNext) autoconfig handler used the scoped package name @opennextjs/cloudflare, which pnpm interprets as a workspace filter rather than a binary name. This caused wrangler deploy --x-autoconfig to fail for pnpm-based Next.js projects with ERR_PNPM_RECURSIVE_EXEC_FIRST_FAIL. Changed to use the unscoped binary name opennextjs-cloudflare, which resolves correctly across all package managers.
#12516 84252b7 Thanks @edmundhung! - Stop proxying localhost requests when proxy environment variables are set

When HTTP_PROXY or HTTPS_PROXY is configured, all fetch requests including ones to localhost were routed through the proxy. This caused wrangler dev and the Vite plugin to fail with "TypeError: fetch failed" because the proxy can't reach local addresses.

This switches from ProxyAgent to undici's EnvHttpProxyAgent, which supports the NO_PROXY environment variable. When NO_PROXY is not set, it defaults to localhost,127.0.0.1,::1 so local requests are never proxied.

The NO_PROXY config only applies to the request destination, not the proxy server address. So a proxy running on localhost (e.g. HTTP_PROXY=http://127.0.0.1:11451) still works for outbound API calls.
#12506 e5efa5d Thanks @sesteves! - Fix wrangler r2 sql query displaying [object Object] for nested values

SQL functions that return complex types such as arrays of objects (e.g. approx_top_k) were rendered as [object Object] in the table output because String() was called directly on non-primitive values. These values are now serialized with JSON.stringify so they display as readable JSON strings.
#11725 be9745f Thanks @dario-piotrowicz! - Fix incorrect logic during autoconfiguration (when running wrangler setup or wrangler deploy --x-autoconfig) that caused parts of the project's package.json file, removed during the process, to incorrectly be added back
#12458 122791d Thanks @jkoe-cf! - Remove default values for delivery delay and message retention and update messaging on limits

Fixes the issue of the default maximum message retention (365400 seconds) being longer than the maximum allowed retention period for free tier users (86400 seconds).

Previous:
- Wrangler set a default value of 365400 seconds max message retention if the setting was not explicitly provided in the Wrangler configuration.
- The maximum retention period was documented as 1209600 seconds for all queues users because it was required to be on paid tier.
- Wrangler also set a default value of 0 seconds for delivery delay if the setting was not explicitly provided in the Wrangler configuration.
Updated:
- Wrangler no longer sets a default value for max message retention so that the default can be applied at the API.
- The maximum retention period is now documented as 86400 seconds for free tier queues and 1209600 seconds for paid tier queues
- Wrangler also no longer sets a default value for delivery delay so that the default can be applied at the API.
#12513 41e18aa Thanks @pombosilva! - Add confirmation prompt when deploying workflows with names that belong to different workers.

When deploying a workflow with a name that already exists and is currently associated with a different worker script, Wrangler will now display a warning and prompt for confirmation before proceeding. This helps prevent accidentally overriding workflows.

In non-interactive environments this check is skipped by default. Use the --strict flag to enable the check in non-interactive environments, which will cause the deployment to fail if workflow conflicts are detected.
Updated dependencies [f7fa326, 7aaa2a5, d06ad09]:
- miniflare@4.20260212.0

`v4.64.0`

Compare Source

Minor Changes

#12433 2acb277 Thanks @martinezjandrew! - Updated registries delete subcommand to handle new API response that now returns a secrets store secret reference after deletion. Wrangler will now prompt the user if they want to delete the associated secret. If so, added new logic to retrieve a secret by its name. The subcommand will then delete the secret.
#12307 e02b5f5 Thanks @dario-piotrowicz! - Improve autoconfig telemetry with granular event tracking

Adds detailed telemetry events to track the autoconfig workflow, including process start/end, detection, and configuration phases. Each event includes a unique session ID (appId), CI detection, framework information, and success/error status to help diagnose issues and understand usage patterns.
#12474 8ba1d11 Thanks @petebacondarwin! - Add wrangler pages deployment delete command to delete Pages deployments via CLI

You can now delete a Pages deployment directly from the command line:
```
wrangler pages deployment delete <deployment-id> --project-name <name>
```
Use the --force (or -f) flag to skip the confirmation prompt, which is useful for CI/CD automation.
#12307 e02b5f5 Thanks @dario-piotrowicz! - Include all common telemetry properties in ad-hoc telemetry events

Previously, only command-based telemetry events (e.g., "wrangler command started/completed") included the full set of common properties. Ad-hoc events sent via sendAdhocEvent were missing important context like OS information, CI detection, and session tracking.

Now, all telemetry events include the complete set of common properties:
- amplitude_session_id and amplitude_event_id for session tracking
- wranglerVersion (and major/minor/patch variants)
- osPlatform, osVersion, nodeVersion
- packageManager
- configFileType
- isCI, isPagesCI, isWorkersCI
- isInteractive
- isFirstUsage
- hasAssets
- agent
#12479 fd902aa Thanks @dario-piotrowicz! - Add framework selection prompt during autoconfig

When running autoconfig in interactive mode, users are now prompted to confirm or change the detected framework. This allows correcting misdetected frameworks or selecting a framework when none was detected, defaulting to "Static" in that case.
#12465 961705c Thanks @petebacondarwin! - Add --json flag to wrangler pages project list command

You can now use the --json flag to output the project list as clean JSON instead of a formatted table. This enables easier programmatic processing and scripting workflows.
```
> wrangler pages project list --json

[
  {
    "Project Name": "my-pages-project",
    "Project Domains": "my-pages-project-57h.pages.dev",
    "Git Provider": "No",
    "Last Modified": "23 hours ago"
  },
  ...
]
```
#12470 21ac7ab Thanks @petebacondarwin! - Add WRANGLER_COMMAND environment variable to custom build commands

When using a custom build command in wrangler.toml, you can now detect whether wrangler dev or wrangler deploy triggered the build by reading the WRANGLER_COMMAND environment variable.

This variable will be set to "dev", "deploy", "versions upload", or "types" depending on which command invoked the build. This allows you to customize your build process based on the deployment context.

Example usage in a build script:
```
if [ "$WRANGLER_COMMAND" = "dev" ]; then
  echo "Building for development..."
else
  echo "Building for production..."
fi
```

Patch Changes

#12468 5d56487 Thanks @petebacondarwin! - Add debug logs for git branch detection in wrangler pages deploy command

When running wrangler pages deploy, the command automatically detects git information (branch, commit hash, commit message, dirty state) from the local repository. Previously, when this detection failed, there was no way to troubleshoot the issue.

Now, running with WRANGLER_LOG=debug will output detailed information about:
- Whether a git repository is detected
- Each git command being executed and its result
- The detected values (branch, commit hash, commit message, dirty status)
- Any errors that occur during detection
Example usage:
```
WRANGLER_LOG=debug wrangler pages deploy ./dist --project-name=my-project
```
#12447 c8dda16 Thanks @dario-piotrowicz! - fix: Throw a descriptive error when autoconfig cannot detect an output directory

When running wrangler setup or wrangler deploy --x-autoconfig on a project where the output directory cannot be detected, you will now see a clear error message explaining what's missing (e.g., "Could not detect a directory containing the static (html, css and js) files for the project") instead of a generic configuration error. This makes it easier to understand and resolve the issue.
#12440 555b32a Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"

The following dependency versions have been updated:

Dependency From To

workerd 1.20260205.0 1.20260206.0
#12485 [d636d6a](https://redirect.github.com/cloudflare/workers-sdk/commit/d636d6a2e

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 becomes conflicted, 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.

This change is

socket-security · 2026-02-13T18:23:06Z

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	wrangler@4.59.1 ⏵ 4.70.0	^-5		^-2

View full report

cloudflare-workers-and-pages · 2026-02-13T18:23:51Z

Deploying with Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	database	`eabd1e1`	Commit Preview URL Branch Preview URL	Mar 03 2026, 10:17 PM

socket-security · 2026-02-19T14:49:40Z

All alerts resolved. Learn more about Socket for GitHub.

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

View full report

renovate bot force-pushed the renovate/wrangler-4.x branch from 7e153ed to bbdd952 Compare February 17, 2026 15:42

renovate bot changed the title ~~Update dependency wrangler to v4.65.0~~ Update dependency wrangler to v4.66.0 Feb 17, 2026

renovate bot force-pushed the renovate/wrangler-4.x branch from bbdd952 to 6dc5805 Compare February 19, 2026 14:49

renovate bot changed the title ~~Update dependency wrangler to v4.66.0~~ Update dependency wrangler to v4.67.0 Feb 19, 2026

renovate bot force-pushed the renovate/wrangler-4.x branch from 6dc5805 to d76624c Compare February 23, 2026 18:59

renovate bot changed the title ~~Update dependency wrangler to v4.67.0~~ Update dependency wrangler to v4.67.1 Feb 23, 2026

renovate bot force-pushed the renovate/wrangler-4.x branch from d76624c to 84ca898 Compare February 23, 2026 22:34

renovate bot changed the title ~~Update dependency wrangler to v4.67.1~~ Update dependency wrangler to v4.68.0 Feb 23, 2026

renovate bot force-pushed the renovate/wrangler-4.x branch from 84ca898 to 0698436 Compare February 24, 2026 18:04

renovate bot changed the title ~~Update dependency wrangler to v4.68.0~~ Update dependency wrangler to v4.68.1 Feb 24, 2026

renovate bot force-pushed the renovate/wrangler-4.x branch from 0698436 to 616a1f8 Compare February 26, 2026 16:48

renovate bot changed the title ~~Update dependency wrangler to v4.68.1~~ Update dependency wrangler to v4.69.0 Feb 26, 2026

Update dependency wrangler to v4.70.0

eabd1e1

renovate bot force-pushed the renovate/wrangler-4.x branch from 616a1f8 to eabd1e1 Compare March 3, 2026 22:17

renovate bot changed the title ~~Update dependency wrangler to v4.69.0~~ Update dependency wrangler to v4.70.0 Mar 3, 2026

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update dependency wrangler to v4.70.0#10

Update dependency wrangler to v4.70.0#10
renovate[bot] wants to merge 1 commit intomainfrom
renovate/wrangler-4.x

renovate bot commented Feb 13, 2026 •

edited by BoomchainLabs

Loading

Uh oh!

socket-security bot commented Feb 13, 2026 •

edited

Loading

Uh oh!

cloudflare-workers-and-pages bot commented Feb 13, 2026 •

edited

Loading

Uh oh!

socket-security bot commented Feb 19, 2026 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Dependency	From	To
workerd	1.20260305.0	1.20260226.1
@cloudflare/workers-types	4.20260305.0	4.20260226.1

Conversation

renovate bot commented Feb 13, 2026 • edited by BoomchainLabs Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Configuration

Uh oh!

socket-security bot commented Feb 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

cloudflare-workers-and-pages bot commented Feb 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Deploying with Cloudflare Workers

Uh oh!

socket-security bot commented Feb 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

renovate bot commented Feb 13, 2026 •

edited by BoomchainLabs

Loading

socket-security bot commented Feb 13, 2026 •

edited

Loading

cloudflare-workers-and-pages bot commented Feb 13, 2026 •

edited

Loading

socket-security bot commented Feb 19, 2026 •

edited

Loading