Skip to content

chore(deps): update dependency wrangler to v4.123.0 - #1006

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

chore(deps): update dependency wrangler to v4.123.0#1006
renovate[bot] wants to merge 1 commit into
devfrom
renovate/wrangler-4.x-lockfile

Conversation

@renovate

@renovate renovate Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
wrangler (source) 4.118.04.123.0 age confidence

Warning

Some dependencies could not be looked up. Check the warning logs for more information.


Release Notes

cloudflare/workers-sdk (wrangler)

v4.123.0

Compare Source

Minor Changes
  • #​15113 b8fd112 Thanks @​BSFishy! - Add local dev simulation for Cloudflare Access ctx.access.getIdentity()

    You can now configure a mock Cloudflare Access identity in wrangler.json so that ctx.access.getIdentity() returns it during local development.

    // wrangler.json
    {
      "access": {
        "dev": {
          "aud": "my-app-aud-tag",
          "identity": {
            "email": "user@example.com",
            "name": "Test User"
          }
        }
      }
    }
  • #​15152 f0f2054 Thanks @​GregBrimble! - [private beta]: Updates the --ignore-defaults flag to --ignore-base-config on wrangler preview commands.

    --ignore-base-config now only takes effect on Preview creation, rather than on each deployment, since Preview base configuration is now copy-on-create rather than inherit-on-deploy.

  • #​14872 339509d Thanks @​dario-piotrowicz! - Add automatic update prompts for out-of-date Cloudflare agent skills

    When Cloudflare skills were previously installed by Wrangler and the upstream cloudflare/skills repository has newer content, Wrangler now offers to update them after eligible commands complete.

    To reduce prompt fatigue, the update check only runs once a month (30 days since the last install or update). Declining suppresses the prompt until the next upstream change.

    When declining an update, Wrangler offers the option to permanently disable future update prompts. This preference is stored globally in ~/.wrangler/agents-skills-install.jsonc. The WRANGLER_NO_SKILLS_UPDATE_PROMPTS=true environment variable can also be used to suppress prompts. The --install-skills flag remains available regardless of these settings.

Patch Changes

v4.122.0

Compare Source

Minor Changes
  • #​15123 d0c976c Thanks @​dependabot! - Detect Node.js compatibility from the compatibility date, now that nodejs_compat is enabled by default

    As of compatibility date 2026-08-04, workerd enables the nodejs_compat and nodejs_compat_v2 compatibility flags by default. Previously these tools only treated Node.js compatibility as enabled when one of those flags was listed explicitly, so a Worker on a compatibility date of 2026-08-04 or later without the flag would get Node.js APIs from the runtime but no Node.js polyfills from the bundler, and process.env could be substituted with an empty object at build time. They now resolve these flags the same way workerd does, and honour no_nodejs_compat to opt out.

    To keep Node.js compatibility switched off on a newer compatibility date, specify both no_nodejs_compat and no_nodejs_compat_v2, since each flag has its own default.

    @cloudflare/vitest-pool-workers needs nodejs_compat_v2 for its own test runner, so it continues to override a project that opts out of it. On a compatibility date that enables the flag anyway, it now drops the opt-out rather than adding the flag back, which workerd would reject — previously this stopped such a project from running any tests at all.

    wrangler types also no longer attributes its @types/node suggestion to "the nodejs_compat flag", which it can now make for Workers that do not set the flag at all.

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

    The following dependency versions have been updated:

    Dependency From To
    @​cloudflare/workers-types ^5.20260804.1 ^5.20260811.1
    workerd 1.20260804.1 1.20260811.1
  • #​15148 0b82b15 Thanks @​jamesopstad! - Ignore a nodejs_compat compatibility flag that the compatibility date already enables

    workerd rejects a compatibility flag that its compatibility date enables by default, so a Worker configured with both a compatibility date of 2026-08-04 or later and nodejs_compat failed to start locally with "The compatibility flag nodejs_compat became the default as of 2026-08-04 so does not need to be specified anymore".

    The redundant nodejs_compat and nodejs_compat_v2 flags are now dropped when starting the runtime, which has no effect on the resulting Worker because the compatibility date enables both anyway. no_nodejs_compat and no_nodejs_compat_v2 still switch Node.js compatibility off, and a flag specified alongside its own opt-out is left alone so that workerd still reports those as contradictory.

  • #​15123 d0c976c Thanks @​dependabot! - Stop adding a redundant nodejs_compat flag to generated Wrangler configurations

    create-cloudflare and wrangler setup write today's date as the compatibility_date, and from 2026-08-04 that already enables nodejs_compat. Adding the flag as well made the generated project fail to start with "The compatibility flag nodejs_compat became the default as of 2026-08-04 so does not need to be specified anymore", so the flag is now only added for earlier compatibility dates.

    create-cloudflare also removes the flag when a template, or a framework's own scaffolder, already wrote it into a configuration that ends up using such a compatibility date, and still installs @types/node for these projects even though there is no longer a flag to detect them by.

    wrangler setup does the same for a wrangler.json(c) that is already in the project: it writes today's date over whatever date that configuration was written for, so a nodejs_compat it finds there is removed as part of writing the file.

  • #​15142 3b02915 Thanks @​penalosa! - Fix remote binding sessions reusing stale binding configurations

    Starting a new remote bindings session that reuses a Worker name no longer picks up the bindings from a previous session, which could cause Binding "..." not found errors.

  • Updated dependencies [d0c976c, d0c976c, 0b82b15, d0c976c, 90dd5e5]:

v4.121.0

Compare Source

Minor Changes
  • #​15079 15cad03 Thanks @​podonnell-dev! - Add Preview base config secret commands

    Wrangler now manages Worker Preview base config secrets with wrangler preview base-config secret put, delete, list, and bulk. These commands update the Worker's previews_base_config.env, keeping shared defaults scoped to all of that Worker's Previews. wrangler preview base-config secret list reads from the Worker's Preview base config and prints secret names with values masked. wrangler preview base-config secret bulk deletes a secret when its value is null, matching wrangler secret bulk.

  • #​15000 731b33a Thanks @​edmundhung! - Allow Wrangler projects to build a Worker once and reuse it in createTestHarness()

    Build the Worker once:

    wrangler deploy --dry-run --outdir ./worker-output

    Then reuse the emitted Worker during test harness startup and reset:

    const server = createTestHarness({
      workers: [
        {
          configPath: "./wrangler.jsonc",
          prebuiltWorkerDir: "./worker-output",
        },
      ],
    });
  • #​14737 e1b5b4b Thanks @​ttoino! - Add email.sending as an event subscription source for queues

    wrangler queues subscription create now accepts --source email.sending alongside two new flags, --zone-id and --domain, which identify the zone and the sending domain (zone apex or a verified subdomain) to subscribe to. Both flags are required for this source. The subscription's resource is displayed as the sending domain in wrangler queues subscription get.

  • #​15073 d669088 Thanks @​FlorentCollin! - Add US jurisdiction support to wrangler d1 create

    You can now create a D1 database in the US jurisdiction with wrangler d1 create <name> --jurisdiction us. The new jurisdiction is also listed in the command's help output.

  • #​15079 15cad03 Thanks @​podonnell-dev! - Use Preview deployment PATCH APIs for Preview secret commands

    Wrangler now updates Worker Preview secrets by patching the named Preview's latest deployment instead of patching the Worker's Previews settings. This keeps secret changes scoped to one Preview, avoids affecting production or other Previews, and creates a new Preview deployment that goes live at 100% immediately. wrangler preview secret list now reads from the named Preview's latest deployment and prints secret names with values masked. wrangler preview secret bulk now deletes a secret when its value is null, matching wrangler secret bulk.

  • #​14924 0aa8fa5 Thanks @​ariesclark! - Honor DO_NOT_TRACK=1 as a telemetry opt-out

    Wrangler now disables telemetry when DO_NOT_TRACK=1 is set, regardless of other telemetry settings.

Patch Changes
  • #​15081 026e058 Thanks @​podonnell-dev! - Compact wrangler preview deployment success output

    wrangler preview now prints a concise success summary with the Preview name, Preview URL, deployment ID, and Deployment URL instead of the previous box-art settings summary.

  • #​15132 5b1b930 Thanks @​dario-piotrowicz! - Fetch script metadata directly instead of listing all scripts

    When resolving Durable Object migrations, fetch the specific script's service metadata via /workers/services/{name} instead of listing all scripts in the account via /workers/scripts. This avoids downloading metadata for every Worker in the account just to find one script's migration tag.

  • #​15032 6e7d37d Thanks @​Sertug17! - Fix wrangler dev commands crashing with No such module "wrangler:modules-watch" when "no_bundle": true

    Running wrangler dev or wrangler pages dev with bundling disabled ("no_bundle": true in wrangler.json, or the --no-bundle flag) no longer crashes at startup with Uncaught Error: No such module "wrangler:modules-watch". Live reloading on file changes continues to work as before.

  • Updated dependencies [c7aede7]:

v4.120.1

Compare Source

Patch Changes

v4.120.0

Compare Source

Minor Changes
  • #​15008 35c87e9 Thanks @​skepticfx! - Adds the ability to find container instances by exact ID or name

    wrangler containers instances <application_id> --search <instance_id_or_name> now searches every page and returns exact matches in human-readable or JSON output. JSON returns a top-level array, including an empty array when there is no match, while human-readable output prints a no-match message. If multiple instances have the same exact name, every matching instance is returned.

  • #​15008 35c87e9 Thanks @​skepticfx! - Add explicit pagination to container instance JSON output

    Use wrangler containers instances <application_id> --json --per-page <size> to return one page with machine-readable result_info, then pass its next_page_token to --page-token to retrieve the next page. Plain --json remains backward-compatible: it requests the complete list and returns the existing top-level array.

Patch Changes
  • #​15013 8cf78c8 Thanks @​dario-piotrowicz! - Update undici from 7.28.0 to 7.29.0

  • #​15015 a60ff4d Thanks @​nickpatt! - Cut the per-request cost of local observability capture

    Every tail event was written to the trace store as its own Durable Object call, so a request paid two or three round-trips per span. On a module-heavy app under the Vite plugin that dominated dev request latency. Rows are now buffered and written in batches, taking a request from roughly thirty calls to three.

    Work in progress still shows up as it happens: the root span is written immediately, console logs and exceptions as they arrive, and a span's completion is written on the next event once 100ms has passed. An invocation that goes completely quiet writes nothing further until it ends, since the flush is driven by tail events rather than a timer.

    The Vite plugin's own router, asset and proxy workers are also no longer captured. Their traces were noise the Observability views already hid, and skipping them cuts the spans recorded per request — a side benefit being that a trace's root is now your Worker rather than __router-worker__.

  • Updated dependencies [b4f0c97, 8cf78c8, a60ff4d, 99eb50c]:

v4.119.0

Compare Source

Minor Changes
  • #​14952 20470fa Thanks @​nelsonjsduarte! - Add --parse-type flag to wrangler ai-search create

    wrangler ai-search create now accepts --parse-type to control how a website data source discovers URLs. sitemap (the default) reads XML sitemaps; discover follows links recursively.

    Previously the parse type could only be chosen through the interactive wizard, which was skipped whenever --source was supplied — so it was impossible to create a discover instance from a script.

    wrangler ai-search create my-instance \
      --type web-crawler \
      --source https://example.com \
      --parse-type discover

    The interactive wizard now offers Discover alongside Sitemap. --parse-type is only valid with --type web-crawler; passing it with --type builtin or --type r2 is rejected, since the API stores the value for those source types but never reads it. When the flag is omitted in non-interactive mode the field is left unset and the API default (sitemap) applies.

  • #​14941 266172b Thanks @​nickpatt! - Improve the Local Explorer's Observability views

    console.log messages now render the way the console would (JSON-encoded strings are unwrapped and multi-argument logs are joined), traces and events can be looked up by trace or span id from the search bar, and an event's "View trace" button jumps to the exact invocation that emitted it — even when a trace_id spans several invocations (e.g. a subrequest or self fetch).

  • #​14064 a9e5abb Thanks @​petebacondarwin! - Add support for OAuth 2.0 Device Authorization Grant to wrangler login

    Run wrangler login --device to authenticate without a local callback server. Useful in containers, remote SSH sessions, Codespaces, and any other environment where localhost:8976 is unreachable from your browser.

    The new flow:

    • prints the verification URL and user code to the terminal,
    • attempts to open the verification URL in your default browser automatically (suppressed via --browser=false),
    • and polls the token endpoint until you approve the request (with a 5-minute hard cap).

    The verification URL is supplied by the authorization server, so it is rejected unless it is an https URL on the same auth domain the device code was requested from — it is never printed or opened otherwise.

    --callback-host and --callback-port cannot be combined with --device, since this flow does not start a local callback server.

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.

@github-actions

github-actions Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Package Changes Through 375fd59

No changes.

Add a change file through the GitHub UI by following this link.


Read about change files or the docs at github.com/jbolda/covector

@socket-security

socket-security Bot commented Aug 5, 2026

Copy link
Copy Markdown

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

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Addednpm/​wrangler@​4.123.0981009296100

View full report

@renovate
renovate Bot force-pushed the renovate/wrangler-4.x-lockfile branch from d3fc3d6 to 63850be Compare August 7, 2026 14:49
@renovate renovate Bot changed the title chore(deps): update dependency wrangler to v4.119.0 chore(deps): update dependency wrangler to v4.120.0 Aug 7, 2026
@renovate
renovate Bot force-pushed the renovate/wrangler-4.x-lockfile branch from 63850be to 98275c2 Compare August 10, 2026 18:28
@renovate renovate Bot changed the title chore(deps): update dependency wrangler to v4.120.0 chore(deps): update dependency wrangler to v4.120.1 Aug 10, 2026
@renovate
renovate Bot force-pushed the renovate/wrangler-4.x-lockfile branch from 98275c2 to c41ea58 Compare August 11, 2026 22:12
@renovate renovate Bot changed the title chore(deps): update dependency wrangler to v4.120.1 chore(deps): update dependency wrangler to v4.121.0 Aug 11, 2026
@renovate
renovate Bot force-pushed the renovate/wrangler-4.x-lockfile branch from c41ea58 to 610b0d0 Compare August 12, 2026 22:41
@renovate renovate Bot changed the title chore(deps): update dependency wrangler to v4.121.0 chore(deps): update dependency wrangler to v4.122.0 Aug 12, 2026
@renovate
renovate Bot force-pushed the renovate/wrangler-4.x-lockfile branch from 610b0d0 to 375fd59 Compare August 13, 2026 20:05
@renovate renovate Bot changed the title chore(deps): update dependency wrangler to v4.122.0 chore(deps): update dependency wrangler to v4.123.0 Aug 13, 2026
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