Skip to content

chore(deps-dev): bump wrangler from 4.98.0 to 4.124.0 - #167

Merged
sarthakagrawal927 merged 1 commit into
mainfrom
dependabot/npm_and_yarn/wrangler-4.124.0
Aug 23, 2026
Merged

chore(deps-dev): bump wrangler from 4.98.0 to 4.124.0#167
sarthakagrawal927 merged 1 commit into
mainfrom
dependabot/npm_and_yarn/wrangler-4.124.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 22, 2026

Copy link
Copy Markdown
Contributor

Bumps wrangler from 4.98.0 to 4.124.0.

Release notes

Sourced from wrangler's releases.

wrangler@4.124.0

Minor Changes

  • #15026 6529f0c Thanks @​petebacondarwin! - Allow containers to be attached to a Durable Object from its exports entry

    A container can now be linked to its Durable Object from the export side, using a new container field that names an entry in the containers array. As a result containers[].class_name is now optional — a container that is referenced this way only needs a name:

    {
      "name": "my-worker",
      "main": "worker.js",
      "compatibility_date": "2026-07-01",
      "containers": [
        { "name": "my-container", "image": "./Dockerfile", "max_instances": 1 }
      ],
      "exports": {
        "MyContainerDO": {
          "type": "durable-object",
          "storage": "sqlite",
          "container": "my-container"
        }
      }
    }

    The existing containers[].class_name direction keeps working and either direction may be used, but the two must agree: a container that names its Durable Object cannot also be claimed by a different one.

    container is only valid on live durable-object exports (created and expecting-transfer) and requires storage: "sqlite". Wrangler now also reports an error when:

    • a container reference names a container that does not exist
    • two Durable Object exports claim the same container
    • a container and a Durable Object export disagree about which one they are linked to
    • a container ends up linked to no Durable Object at all
    • two containers share a name
    • a container's class_name names a Durable Object whose storage is legacy-kv
    • two containers are attached to the same Durable Object

    That last case was previously accepted but could never work: workerd attaches a single container per Durable Object namespace, and in local development every container for a class builds into the same image tag, so one silently overwrote the other. If you have two containers on one class_name, give each its own Durable Object class.

Patch Changes

  • #15211 bc5726b Thanks @​nithin42! - Honor access.dev when running Workers with @cloudflare/vitest-pool-workers, so ctx.access.getIdentity() returns the configured identity just as it does with wrangler dev.

  • #14999 ba54f0d Thanks @​mittalpk! - Fix .env loading on Windows leaking stale, differently-cased duplicate keys

    On Windows, wrangler loads .env values through a case-insensitive Proxy wrapper so lookups like env.PATH and env.Path resolve to the same value, and this object is assigned directly to process.env. When a key was set again under a different casing (e.g. a value in .env.local overriding one from .env with different casing), the previous casing was never removed from the underlying object. env.PATH/env.Path still returned the correct, latest value, but anything that enumerates process.envObject.keys, for...in, JSON.stringify, object spread, or a spawned subprocess inheriting the environment — would see both the stale and current key.

    Duplicate entries no longer appear, so environment variables passed to subprocesses and any code that lists the environment now see only the latest value for each variable.

  • #15044 b7422b0 Thanks @​stareezy-1! - Normalize structural CRLF line endings before sending D1 commands to the remote query API

... (truncated)

Commits
  • 8ee43f6 Version Packages (#15175)
  • f431166 Prevent date-enabled Node.js compatibility from adding conflicting globals to...
  • 1552bce [wrangler] Quieten warnings and stray output in tests (#15209)
  • bc5726b Pass access.dev through to Miniflare via `unstable_getMiniflareWorkerOptions(...
  • e967c39 [wrangler] Skip container deploy e2e tests on non-Linux CI (#15233)
  • 265256a WC-5744 [previews] fix: wrangler preview base-config flag inheritance (#15153)
  • 75cf407 [wrangler] Enable new config for cf dev (#15082)
  • 8fb2b87 [wrangler] Use FedRAMP container registries (#15196)
  • ba54f0d [wrangler] Fix case-insensitive-env leaking stale duplicate keys on override ...
  • 7cee278 [wrangler] Let CLOUDFLARE_ACCOUNT_ID override the cached account id in pages ...
  • Additional commits viewable in compare view

@dependabot @github

dependabot Bot commented on behalf of github Aug 22, 2026

Copy link
Copy Markdown
Contributor Author

Labels

The following labels could not be found: ccusage, dependencies. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

Bumps [wrangler](https://github.com/cloudflare/workers-sdk/tree/HEAD/packages/wrangler) from 4.98.0 to 4.124.0.
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.124.0/packages/wrangler)

---
updated-dependencies:
- dependency-name: wrangler
  dependency-version: 4.124.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/wrangler-4.124.0 branch from ac153be to 92f4f27 Compare August 23, 2026 15:56
@sarthakagrawal927
sarthakagrawal927 merged commit 67f9c99 into main Aug 23, 2026
3 checks passed
@sarthakagrawal927
sarthakagrawal927 deleted the dependabot/npm_and_yarn/wrangler-4.124.0 branch August 23, 2026 16: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.

1 participant