Skip to content

Update dependency wrangler to v4.126.0 - #35

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/wrangler-4.x
Open

Update dependency wrangler to v4.126.0#35
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/wrangler-4.x

Conversation

@renovate

@renovate renovate Bot commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
wrangler (source) 4.125.04.126.0 age confidence

Release Notes

cloudflare/workers-sdk (wrangler)

v4.126.0

Compare Source

Minor Changes
  • #​15332 d1cc3af Thanks @​pombosilva! - Add default_retention to Workflow bindings for configuring how long instances are retained

    Workflow instances are retained for an account-wide default period after they finish. You can now set a per-Workflow default in your Wrangler configuration, applied to instances that do not specify their own retention:

    {
      "workflows": [
        {
          "binding": "MY_WORKFLOW",
          "name": "my-workflow",
          "class_name": "MyWorkflow",
          "default_retention": {
            "success_retention": "3 days",
            "error_retention": "7 days"
          }
        }
      ]
    }

    Each side is optional and accepts either a duration string such as "3 days" or a whole number of milliseconds. Durations are interpreted by the Workflows API, which also caps them at your account's retention limit.

  • #​15064 693ca29 Thanks @​tpmmorris! - Include a chronological list of handler events in email test harness results, so programmatic local email tests can assert the order in which messages are received, forwarded, replied to, or rejected.

    const result = await server.getWorker().email({
      from: "sender@example.com",
      to: "inbox@example.com",
      raw: [
        "From: Sender <sender@example.com>",
        "To: Inbox <inbox@example.com>",
        "Message-ID: <test@example.com>",
        "Subject: Test email",
        "",
        "Hello from the test harness",
      ].join("\r\n"),
    });
    
    expect(result.events).toEqual([
      { type: "received", timestamp: expect.any(String) },
      {
        type: "forward",
        timestamp: expect.any(String),
        messageId: expect.any(String),
      },
      {
        type: "reply",
        timestamp: expect.any(String),
        messageId: expect.any(String),
      },
    ]);
  • #​15065 ad89456 Thanks @​mtlemilio! - Add experimental wrangler hyperdrive planetscale signature for provisioning Cloudflare-billed PlanetScale databases

    wrangler hyperdrive planetscale signature prints a signed authorization as JSON, proving to PlanetScale that Cloudflare will be billed for the database you are about to create:

    npx wrangler hyperdrive planetscale signature | \
      pscale database create <name> \
        --org <org> \
        --engine postgresql \
        --cloudflare-billing @- \
        --format json

    pscale database create defaults to Vitess, so pass --engine postgresql for a Postgres database, and --format json is recommended when the output is consumed by an agent.

    This requires pscale v0.313.0 or newer. Wrangler authorizes the Cloudflare billing side only, so your PlanetScale credentials stay between you and pscale.

    The signature is a cryptographically signed token that authorizes creating a database billed to your Cloudflare account. Treat it as a credential and do not share it. Piping it, as above, is recommended over passing it as a command line argument.

    This command is experimental and its interface may change.

  • #​15134 c66d2d5 Thanks @​gpanders! - Enable FUSE-capable local container development

    Miniflare now automatically passes the Docker privileges needed for FUSE to local Durable Object containers when using local rootless Docker on Linux with /dev/fuse available, or a local Docker engine on macOS or through WSL where Linux containers run in a VM. This applies to Wrangler, the Cloudflare Vite plugin, and direct Miniflare use.

  • #​15326 9fcb1c9 Thanks @​jamesopstad! - Record the selected mode in the Build Output Specification top-level config.json

    The mode a build was produced in is now written to .cloudflare/output/v0/config.json as a mode field, alongside the account and compliance settings.

  • #​14966 a4c3458 Thanks @​yomna-shousha! - Add pull request metadata to wrangler preview deployments

    wrangler preview now detects the pull request associated with the current CI run (GitHub Actions, GitLab CI, CircleCI, and a generic PULL_REQUEST_URL/PR_URL/CHANGE_URL fallback) and attaches it, along with the repository URL, to the preview deployment as annotations (workers/pull_request_number, workers/pull_request_url, workers/repository_url).

    This is best effort: if no pull request can be detected, nothing changes. When a pull request is detected, its URL is now also shown in the wrangler preview command output.

  • #​15307 433fa98 Thanks @​for-the-kidz! - Add pull request title to wrangler preview deployment annotations

    wrangler preview now also detects the title of the pull/merge request associated with the current CI run (GitHub Actions and GitLab CI, plus a generic PULL_REQUEST_TITLE fallback) and attaches it to the preview deployment as the workers/pull_request_title annotation, alongside the existing pull request number/URL, repository URL, and commit SHA annotations.

    This is best effort: if no pull request title can be detected, nothing changes.

Patch Changes

Configuration

📅 Schedule: (UTC)

  • 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 d71ed7f to 88cb502 Compare July 21, 2026 22:49
@renovate renovate Bot changed the title Update dependency wrangler to v4.112.0 Update dependency wrangler to v4.113.0 Jul 21, 2026
@renovate
renovate Bot force-pushed the renovate/wrangler-4.x branch from 88cb502 to 42b9ab5 Compare July 23, 2026 19:40
@renovate renovate Bot changed the title Update dependency wrangler to v4.113.0 Update dependency wrangler to v4.114.0 Jul 23, 2026
@renovate
renovate Bot force-pushed the renovate/wrangler-4.x branch from 42b9ab5 to 9048bb1 Compare July 28, 2026 21:56
@renovate renovate Bot changed the title Update dependency wrangler to v4.114.0 Update dependency wrangler to v4.115.0 Jul 28, 2026
@renovate
renovate Bot force-pushed the renovate/wrangler-4.x branch from 9048bb1 to 3703425 Compare July 30, 2026 16:55
@renovate renovate Bot changed the title Update dependency wrangler to v4.115.0 Update dependency wrangler to v4.116.0 Jul 30, 2026
@renovate
renovate Bot force-pushed the renovate/wrangler-4.x branch from 3703425 to 085711f Compare July 31, 2026 16:04
@renovate renovate Bot changed the title Update dependency wrangler to v4.116.0 Update dependency wrangler to v4.118.0 Jul 31, 2026
@renovate
renovate Bot force-pushed the renovate/wrangler-4.x branch from 085711f to 628ba33 Compare August 5, 2026 14:46
@renovate renovate Bot changed the title Update dependency wrangler to v4.118.0 Update dependency wrangler to v4.119.0 Aug 5, 2026
@renovate
renovate Bot force-pushed the renovate/wrangler-4.x branch from 628ba33 to b135292 Compare August 7, 2026 14:29
@renovate renovate Bot changed the title Update dependency wrangler to v4.119.0 Update dependency wrangler to v4.120.0 Aug 7, 2026
@renovate
renovate Bot force-pushed the renovate/wrangler-4.x branch from b135292 to 46e7394 Compare August 10, 2026 18:57
@renovate renovate Bot changed the title Update dependency wrangler to v4.120.0 Update dependency wrangler to v4.120.1 Aug 10, 2026
@renovate
renovate Bot force-pushed the renovate/wrangler-4.x branch from 46e7394 to 27d3b2c Compare August 11, 2026 22:07
@renovate renovate Bot changed the title Update dependency wrangler to v4.120.1 Update dependency wrangler to v4.121.0 Aug 11, 2026
@renovate
renovate Bot force-pushed the renovate/wrangler-4.x branch from 27d3b2c to 91499a7 Compare August 12, 2026 17:44
@renovate renovate Bot changed the title Update dependency wrangler to v4.121.0 Update dependency wrangler to v4.122.0 Aug 12, 2026
@renovate
renovate Bot force-pushed the renovate/wrangler-4.x branch from 91499a7 to 1bd5405 Compare August 13, 2026 17:12
@renovate renovate Bot changed the title Update dependency wrangler to v4.122.0 Update dependency wrangler to v4.123.0 Aug 13, 2026
@renovate
renovate Bot force-pushed the renovate/wrangler-4.x branch 2 times, most recently from 30c6935 to b59e20b Compare August 18, 2026 16:09
@renovate renovate Bot changed the title Update dependency wrangler to v4.123.0 Update dependency wrangler to v4.124.0 Aug 18, 2026
@renovate
renovate Bot force-pushed the renovate/wrangler-4.x branch from b59e20b to 5f20da0 Compare August 20, 2026 18:12
@renovate renovate Bot changed the title Update dependency wrangler to v4.124.0 Update dependency wrangler to v4.125.0 Aug 20, 2026
@renovate
renovate Bot force-pushed the renovate/wrangler-4.x branch from b59e20b to 5f20da0 Compare August 20, 2026 18:13
@renovate renovate Bot changed the title Update dependency wrangler to v4.125.0 Update dependency wrangler to v4.125.0 - autoclosed Aug 21, 2026
@renovate renovate Bot closed this Aug 21, 2026
@renovate
renovate Bot deleted the renovate/wrangler-4.x branch August 21, 2026 04:08
@renovate renovate Bot changed the title Update dependency wrangler to v4.125.0 - autoclosed Update dependency wrangler to v4.126.0 Aug 25, 2026
@renovate renovate Bot reopened this Aug 25, 2026
@renovate
renovate Bot force-pushed the renovate/wrangler-4.x branch 2 times, most recently from 5f20da0 to 0789a56 Compare August 25, 2026 23:10
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