Skip to content

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 13, 2025

This PR contains the following updates:

Package Change Age Confidence
wrangler (source) ^3.47.1 -> ^4.0.0 age confidence

Release Notes

cloudflare/workers-sdk (wrangler)

v4.42.2

Compare Source

Patch Changes
  • #​10881 ce832d5 Thanks @​garvit-gupta! - Add table-level compaction commands for R2 Data Catalog:

    • wrangler r2 bucket catalog compaction enable <bucket> [namespace] [table]
    • wrangler r2 bucket catalog compaction disable <bucket> [namespace] [table]

    This allows you to enable and disable automatic file compaction for a specific R2 data catalog table.

  • #​10888 d0ab919 Thanks @​lrapoport-cf! - Clarify that wrangler check startup generates a local CPU profile

  • Updated dependencies [42e256f, 4462bc1]:

    • miniflare@​4.20251008.0

v4.42.1

Compare Source

Patch Changes

v4.42.0

Compare Source

Minor Changes
Patch Changes

v4.41.0

Compare Source

Minor Changes
  • #​10507 21a0bef Thanks @​dario-piotrowicz! - Add strict mode for the wrangler deploy command

    Add a new flag: --strict that makes the wrangler deploy command be more strict and not deploy workers when the deployment could be potentially problematic. This "strict mode" currently only affects non-interactive sessions where conflicts with the remote settings for the worker (for example when the worker has been re-deployed via the dashboard) will cause the deployment to fail instead of automatically overriding the remote settings.

  • #​10710 7f2386e Thanks @​penalosa! - Add prompt to resource creation flow allowing for newly created resources to be remote.

Patch Changes

v4.40.3

Compare Source

Patch Changes

v4.40.2

Compare Source

Patch Changes

v4.40.1

Compare Source

Patch Changes

v4.40.0

Compare Source

Minor Changes
  • #​10743 a7ac751 Thanks @​jonesphillip! - Changes --fileSizeMB to --file-size for wrangler r2 bucket catalog compaction command.
    Small fixes for pipelines commands.
Patch Changes
  • #​10706 81fd733 Thanks @​1000hz! - Fixed an issue that caused some Workers to have an incorrect service tag applied when using a redirected configuration file (as used by the Cloudflare Vite plugin). This resulted in these Workers not being correctly grouped with their sibling environments in the Cloudflare dashboard.

  • Updated dependencies [06e9a48]:

    • miniflare@​4.20250924.0

v4.39.0

Compare Source

Minor Changes
  • #​10647 555a6da Thanks @​efalcao! - VPC service binding support

  • #​10612 97a72cc Thanks @​jonesphillip! - Added new pipelines commands (pipelines, streams, sinks, setup), moved old pipelines commands behind --legacy

  • #​10652 acd48ed Thanks @​edmundhung! - Rename Hyperdrive local connection string environment variable from WRANGLER_HYPERDRIVE_LOCAL_CONNECTION_STRING_<BINDING_NAME> to CLOUDFLARE_HYPERDRIVE_LOCAL_CONNECTION_STRING_<BINDING_NAME>. The old variable name is still supported but will now show a deprecation warning.

  • #​10721 55a10a3 Thanks @​penalosa! - Stabilise Worker Loader bindings

Patch Changes

v4.38.0

Compare Source

Minor Changes
Patch Changes

v4.37.1

Compare Source

Patch Changes
  • #​10658 3029b9a Thanks @​1000hz! - Fixed an issue with service tags not being applied properly to Workers when the Wrangler configuration file did not include a top-level name property.

  • #​10657 31ec996 Thanks @​penalosa! - Disable remote bindings with the --local flag

  • Updated dependencies [783afeb]:

    • miniflare@​4.20250913.0

v4.37.0

Compare Source

Minor Changes
  • #​10546 d53a0bc Thanks @​1000hz! - On deploy or version upload, Workers with multiple environments are tagged with metadata that groups them together in the Cloudflare Dashboard.

  • #​10596 735785e Thanks @​penalosa! - Add Miniflare & Wrangler support for unbound Durable Objects

  • #​10622 15c34e2 Thanks @​nagraham! - Modify R2 Data Catalog compaction commands to enable/disable for Catalog (remove table/namespace args), and require Cloudflare API token on enable.

Patch Changes
  • Updated dependencies [735785e]:
    • miniflare@​4.20250906.2

v4.36.0

Compare Source

Minor Changes
Patch Changes

v4.35.0

Compare Source

Minor Changes
  • #​10491 5cb806f Thanks @​zebp! - Add traces, OTEL destinations, and configurable persistence to observability settings

    Adds a new traces field to the observability settings in your Worker configuration that configures the behavior of automatic tracing. Both traces and logs support providing a list of OpenTelemetry compliant destinations where your logs/traces will be exported to as well as an implicitly-enabled persist option that controls whether or not logs/traces are persisted to the Cloudflare observability platform and viewable in the Cloudflare dashboard.

Patch Changes

v4.34.0

Compare Source

Minor Changes
  • #​10478 cc47b51 Thanks @​danielrs! - Beta feature preview_urls is now disabled by default.

    This change makes preview_urls disabled by default when it's not provided, making
    the feature opt-in instead of opt-out.

Patch Changes

v4.33.2

Compare Source

Patch Changes

v4.33.1

Compare Source

Patch Changes

v4.33.0

Compare Source

Minor Changes
Patch Changes

v4.32.0

Compare Source

Minor Changes
  • #​10354 da40571 Thanks @​edmundhung! - Enable cross-process communication for wrangler dev with multiple config files

    Workers running in separate wrangler dev sessions can now communicate with each other regardless of whether you are running with single or multiple config files.

    Check out the Developing with multiple Workers guide to learn more about the different approaches and when to use each one.

  • #​10012 4728c68 Thanks @​penalosa! - Support unsafe dynamic worker loading bindings

Patch Changes
  • #​10245 d304055 Thanks @​edmundhung! - Migrate wrangler dev to use Miniflare dev registry implementation

    Updated wrangler dev to use a shared dev registry implementation that now powers both the Cloudflare Vite plugin and Wrangler. This internal refactoring has no user-facing changes but consolidates registry logic for better consistency across tools.

  • #​10407 f534c0d Thanks @​emily-shen! - default containers.rollout_active_grace_period to 0

  • #​10425 0a96e69 Thanks @​dario-piotrowicz! - Fix debugging logs not including headers for CF API requests and responses

    Fix the fact that wrangler, when run with the WRANGLER_LOG=DEBUG and WRANGLER_LOG_SANITIZE=false environment variables, displays {} instead of the actual headers for requests and responses for CF API fetches

  • #​10337 f9f7519 Thanks @​emily-shen! - containers: rollout_step_percentage now also accepts an array of numbers. Previously it accepted a single number, and each rollout step would target the same percentage of instances. Now users can customise percentages for each step.

    rollout_step_percentage also now defaults to [10,100] (previously 25), which should make rollouts progress slightly faster.

    You can also use wrangler deploy --containers-rollout=immediate to override rollout settings in Wrangler configuration and update all instances in one step. Note this doesn't override rollout_active_grace_period if configured.

  • Updated dependencies [4728c68]:

    • miniflare@​4.20250816.1

v4.31.0

Compare Source

Minor Changes
  • #​10314 9b09751 Thanks @​dario-piotrowicz! - Show possible local vs. dashboard diff information on deploys

    When re-deploying a Worker using wrangler deploy, if the configuration has been modified in the Cloudflare dashboard, the local configuration will overwrite the remote one. This can lead to unexpected results for users. To address this, currently wrangler deploy warns users about potential configuration overrides (without presenting them) and prompts them to confirm whether they want to proceed.

    The changes here improve the above flow in the following way:

    • If the local changes only add new configurations (without modifying or removing existing ones), the deployment proceeds automatically without warnings or prompts, as these changes are non-destructive and safe.
    • If the local changes modify or remove existing configurations, wrangler deploy now displays a git-like diff showing the differences between the dashboard and local configurations. This allows users to review and understand the impact of their changes before confirming the deployment.
  • #​10334 cadf19a Thanks @​jonesphillip! - Added queues subscription command to Wrangler including create, update, delete, get, list

Patch Changes
  • #​10374 20520fa Thanks @​edmundhung! - Simplify debug package resolution with nodejs_compat

    A patched version of debug was previously introduced that resolved the package to a custom implementation. However, this caused issues due to CJS/ESM interop problems. We now resolve the debug package to use the Node.js implementation instead.

  • #​10249 875197a Thanks @​penalosa! - Support JSRPC for remote bindings. This unlocks:

    • JSRPC over Service Bindings
    • JSRPC over Dispatch Namespace Bindings
    • Email
    • Pipelines
  • Updated dependencies [565c3a3, ddadb93, 20520fa, 875197a]:

v4.30.0

Compare Source

Minor Changes
Patch Changes
  • #​10217 979984b Thanks @​veggiedefender! - Increase the maxBuffer size for capnp uploads

  • #​10356 80e964c Thanks @​WillTaylorDev! - fix: Update regex for valid branch name to remove 61 char length requirement, allowing for longer branch names to be specified for preview aliases.

  • #​10289 a5a1426 Thanks @​emily-shen! - Cleanup container images created during local dev if no changes have been made.

    We now untag old images that were created by Wrangler/Vite if we find that the image content and configuration is unchanged, so that we don't keep accumulating image tags.

  • #​10315 0c04da9 Thanks @​emily-shen! - Add rollout_active_grace_period option to containers configuration.

    This allows users to configure how long an active container should keep running for during a rollout, before the upgrade is applied.

  • #​10321 b524a6f Thanks @​emily-shen! - print prettier errors during container deployment

  • #​10253 eb32a3a Thanks @​emily-shen! - fix redeploying container apps when previous deploy failed or container (but not image) was deleted.

    Previously this failed with No changes detected but no previous image found as we assumed there would be a previous deployment when an image exists in the registry.

  • #​9990 4288a61 Thanks @​penalosa! - Fix startup profiling when sourcemaps are enabled

  • Updated dependencies [d54d8b7, ae0c806]:

    • miniflare@​4.20250813.1

v4.29.1

Compare Source

Patch Changes
  • Updated dependencies [5020694]:
    • miniflare@​4.20250813.0

v4.29.0

Compare Source

Minor Changes
Patch Changes
  • #​10232 e7cae16 Thanks @​emily-shen! - fix: validate wrangler containers delete ID to ensure a valid ID has been provided. Previously if you provided the container name (or any non-ID shaped string) you would get an auth error instead of a 404.

  • #​10139 3b6ab8a Thanks @​dom96! - Removes mention of cf-requirements when Python Workers are enabled

  • #​10259 c58a05c Thanks @​dario-piotrowicz! - Ensure that maybeStartOrUpdateRemoteProxySession considers the potential account_id from the user's wrangler config

    Currently if the user has an account_id in their wrangler config file, such id won't be taken into consideration for the remote proxy session, the changes here make sure that it is (note that the auth option of maybeStartOrUpdateRemoteProxySession, if provided, takes precedence over this id value).

    The changes here also fix the same issue for wrangler dev and getPlatformProxy (since they use maybeStartOrUpdateRemoteProxySession under the hook).

  • #​10288 42aafa3 Thanks @​tgarg-cf! - Do not attempt to update queue producer settings when deploying a Worker with a queue binding

    Previously, each deployed Worker would update a subset of the queue producer's settings for each queue binding, which could result in broken queue producers or at least conflicts where different Workers tried to set diffe


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.

@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 3 times, most recently from abecd31 to 1bb596f Compare July 28, 2025 18:25
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 3 times, most recently from 4bb912e to a7fb2d1 Compare August 5, 2025 09:58
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 4 times, most recently from 730d399 to 7c901c7 Compare August 13, 2025 16:41
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 4 times, most recently from 156672a to e0c53bf Compare August 21, 2025 16:36
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 2 times, most recently from 611aca4 to 54d78e2 Compare August 28, 2025 17:40
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 2 times, most recently from 8adbdd4 to 91bc601 Compare September 9, 2025 14:47
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 4 times, most recently from e24c9dd to 486333f Compare September 18, 2025 17:26
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 5 times, most recently from 9c50ebb to e573f02 Compare September 30, 2025 14:39
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 2 times, most recently from 1bf7a62 to 666cfdf Compare October 3, 2025 16:48
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 2 times, most recently from 4352644 to 0e0869c Compare October 7, 2025 17:51
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from 0e0869c to f94920c Compare October 9, 2025 18:07
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.

0 participants