Skip to content

chore(deps): update dependency wrangler to v4 #220

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(deps): update dependency wrangler to v4 #220

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 13, 2025 •
edited
Loading

This PR contains the following updates:

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

Release Notes

cloudflare/workers-sdk (wrangler)

v4.44.0

Compare Source

Minor Changes

  • #​10939 d4b4c90 Thanks @​danielrs! - Config preview_urls defaults to workers_dev value.

    Originally, we were defaulting config.preview_urls to true, but we
    were accidentally enabling Preview URLs for users that only had
    config.workers_dev=false.

    Then, we set the default value of config.preview_urls to false, but we
    were accidentally disabling Preview URLs for users that only had
    config.workers_dev=true.

    Rather than defaulting config.preview_urls to true or false, we
    default to the resolved value of config.workers_dev. Should result in a
    clearer user experience.

  • #​11027 1a2bbf8 Thanks @​jamesopstad! - Statically replace the value of process.env.NODE_ENV with development for development builds and production for production builds if it is not set. Else, use the given value. This ensures that libraries, such as React, that branch code based on process.env.NODE_ENV can be properly tree shaken.

  • #​9705 0ee1a68 Thanks @​hiendv! - Add params type to Workflow type generation. E.g.

    interface Env {
	MY_WORKFLOW: Workflow<
		Parameters<import("./src/index").MyWorkflow["run"]>[0]["payload"]
	>;
}

  • #​10867 dd5f769 Thanks @​austin-mc! - Add media binding support

Patch Changes

  • #​11018 5124818 Thanks @​dario-piotrowicz! - Improve potential errors thrown by startRemoteProxySession by including more information

  • #​11019 6643bd4 Thanks @​dario-piotrowicz! - Fix observability.logs.persist being flagged as an unexpected field during the wrangler config file validation

  • #​10768 8211bc9 Thanks @​dario-piotrowicz! - Update logs handling to use the new handleStructuredLogs miniflare option

  • #​10997 3bb034f Thanks @​nikitassharma! - When either WRANGLER_OUTPUT_FILE_PATH or WRANGLER_OUTPUT_FILE_DIRECTORY are set
    in the environment, then command failures will append a line to the output file
    encoding the error code and message, if present.

  • #​10986 43503c7 Thanks @​emily-shen! - fix: cleanup any running containers again on wrangler dev exit

  • #​11000 a6de9db Thanks @​jonboulle! - always load container image into local store during build

    BuildKit supports different build drivers. When using the more modern docker-container driver (which is now the default on some systems, e.g. a standard Docker installation on Fedora Linux), it will not automatically load the built image into the local image store. Since wrangler expects the image to be there (e.g. when calling getImageRepoTags), it will thus fail, e.g.:

    ⎔ Preparing container image(s)...
[+] Building 0.3s (8/8) FINISHED                                                                                                                                                                                                     docker-container:default

[...]

WARNING: No output specified with docker-container driver. Build result will only remain in the build cache. To push result image into registry use --push or to load image into docker use --load

✘ [ERROR] failed inspecting image locally: Error response from daemon: failed to find image cloudflare-dev/sandbox:f86e40e4: docker.io/cloudflare-dev/sandbox:f86e40e4: No such image

    Explicitly setting the --load flag (equivalent to -o type=docker) during the build fixes this and should make the build a bit more portable without requiring users to change their default build driver configuration.

  • #​10994 d39c8b5 Thanks @​pombosilva! - Make Workflows instances list command cursor based

  • #​10892 7d0417b Thanks @​dario-piotrowicz! - improve the diffing representation for wrangler deploy (run under --x-remote-diff-check)

  • Updated dependencies [36d7054, dd5f769, ee7d710, 8211bc9]:

v4.43.0

Compare Source

Minor Changes
Patch Changes

  • #​10938 e52d0ec Thanks @​penalosa! - Acquire Cloudflare Access tokens for additional requests made during a wrangler dev --remote session

  • #​10923 2429533 Thanks @​emily-shen! - fix: update docker manifest inspect to use full image registry uri when checking if the image exists remotely

  • #​10521 88b5b7f Thanks @​penalosa! - Improves the Wrangler auto-provisioning feature (gated behind the experimental flag --x-provision) by:

    • Writing back changes to the user's config file (not necessary, but can make it resilient to binding name changes)
    • Fixing --dry-run, which previously threw an error when your config file had auto provisioned resources
    • Improve R2 bindings display to include the bucket_name from the config file on upload
    • Fixing bindings view for specific versions to not display TOML

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, lis

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 ba45832 to 9f1cd21 Compare July 29, 2025 10:52
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 2 times, most recently from 6934c08 to bbf98d5 Compare August 5, 2025 09:54
@coderabbitai coderabbitai
Copy link

coderabbitai bot commented Aug 5, 2025 •
edited
Loading

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch renovate/wrangler-4.x
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 3 times, most recently from 009e7f2 to bc0a367 Compare August 13, 2025 17:08
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 2 times, most recently from 766d424 to 176a551 Compare August 18, 2025 19:06
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 3 times, most recently from 935fd56 to 8089e68 Compare August 28, 2025 17:53
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 3 times, most recently from ec89b32 to 96f2697 Compare September 9, 2025 13:54
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 4 times, most recently from e013009 to 2a21a55 Compare September 18, 2025 14:30
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 5 times, most recently from 6f029b3 to 8c9b048 Compare September 30, 2025 13:02
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 3 times, most recently from 9337ebe to 2fd9fc4 Compare October 7, 2025 18:51
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from 2fd9fc4 to 86ff565 Compare October 9, 2025 17:12
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from 86ff565 to f899bbc Compare October 14, 2025 18:34
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from f899bbc to cf40ce6 Compare October 21, 2025 20:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants