build(deps-dev): bump the cloudflare-toolchain group across 1 directory with 4 updates by dependabot[bot] · Pull Request #37 · Victoria824/QueryAssure

dependabot · 2026-08-24T13:13:09Z

Bumps the cloudflare-toolchain group with 4 updates in the / directory: @cloudflare/vite-plugin, vinext, vite and wrangler.

Updates @cloudflare/vite-plugin from 1.52.1 to 1.53.1

Release notes

Sourced from @cloudflare/vite-plugin's releases.

@cloudflare/vite-plugin@1.53.1

Patch Changes

Updated dependencies [59872c4, c68f9cb, 99a1f49, 5ae9d5b, 4b52975, ce9b151, ef73a28, 649f667, 39dcea6, 99a1f49, 99a1f49, 99a1f49, f2437e6, 30c2d47]:

wrangler@4.125.0

miniflare@5.20260820.0-alpha

@cloudflare/vite-plugin@1.53.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

#15238 3a4fc6b Thanks @jamesopstad! - Honor access.dev when running Workers with @cloudflare/vite-plugin, so ctx.access.getIdentity() returns the configured identity.

... (truncated)

Changelog

Sourced from @cloudflare/vite-plugin's changelog.

1.53.1

Patch Changes

Updated dependencies [59872c4, c68f9cb, 99a1f49, 5ae9d5b, 4b52975, ce9b151, ef73a28, 649f667, 39dcea6, 99a1f49, 99a1f49, 99a1f49, f2437e6, 30c2d47]:

wrangler@4.125.0

miniflare@5.20260820.0-alpha

1.53.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

... (truncated)

Commits

38b4623 Version Packages (#15250)
8ee43f6 Version Packages (#15175)
1552bce [wrangler] Quieten warnings and stray output in tests (#15209)
3a4fc6b Pass access configuration to Router Worker (#15238)
8fb2b87 [wrangler] Use FedRAMP container registries (#15196)
d4f441f [vite-plugin-cloudflare] Handle cancelled request bodies (#15028)
1f79ace Use a fixed default compatibility date derived from the pinned workerd (#15185)
6529f0c [wrangler] Allow containers to be attached to Durable Objects via exports (...
See full diff in compare view

Updates vinext from 1.0.0-beta.6 to 1.0.0-beta.8

Release notes

Sourced from vinext's releases.

vinext@1.0.0-beta.8

Features

experimental support for React Compiler via react: { compiler: true } (#3005)

Bug Fixes

Build: avoid workerd cwd in module identity (#3007)

Contributors

@james-elicx

@jlucaso1

vinext@1.0.0-beta.7

Bug Fixes

App Router

route server actions through their owning pages (#2520)

restore shallow history tree snapshots (#2885)

preserve static hydration search params (#2944)

settle optimistic search navigations (#2952)

retain shared layouts across loading shells (#2940)

match current navigation identity (#2876)

retain loading shell prefetches (#2938)

Build

preserve bundled ESM module identity (#2942)

preserve portable CommonJS module identity (#2826)

preserve require export conditions (#2881)

support deployed web worker graphs (#2314)

make vinext shim chunk rule reachable for installed copies (#2795)

Misc

Cache: inherit route revalidate for tagged fetches (#2985)

Security: validate supplemental interception selectors (#2976)

Router: refresh retained parallel routes (#2880)

Pages Router: emit dev build ID in next data (#2962)

Cache: reject unserializable use cache results (#2954)

Pages: align GSSP client transitions (#2240)

Fonts: normalize self-hosted URLs on Windows (#2934)

RSC: web crypto subtle api is unavailable in non-secure contexts (#2929)

Contributors

@james-elicx

@Jbithell

... (truncated)

Commits

20fdac4 chore: version packages (beta) (#3008)
52c81f3 feat: experimental support for React Compiler via react: { compiler: true } (...
c107079 fix(build): avoid workerd cwd in module identity (#3007)
7ed5570 fix(test): avoid fixture server localhost DNS race (#2999)
b7a42ec fix(test): mark hybrid i18n fixture private (#2998)
87f6ec4 chore: version packages (beta) (#2930)
ff3b722 chore(release): suppress web SEO commit from package release (#2997)
0736fdd fix(app-router): route server actions through their owning pages (#2520)
6736c31 Use GPT-5.6 Terra and Sol for Bonk (#2987)
9a87632 fix(web): consolidate canonical host SEO signals (#2989)
Additional commits viewable in compare view

Updates vite from 8.1.5 to 8.2.2

Release notes

Sourced from vite's releases.

plugin-legacy@8.2.2

Please refer to CHANGELOG.md for details.

v8.2.2

Please refer to CHANGELOG.md for details.

plugin-legacy@8.2.1

Please refer to CHANGELOG.md for details.

v8.2.1

Please refer to CHANGELOG.md for details.

create-vite@8.2.0

Please refer to CHANGELOG.md for details.

plugin-legacy@8.2.0

Please refer to CHANGELOG.md for details.

v8.2.0

Please refer to CHANGELOG.md for details.

v8.2.0-beta.0

Please refer to CHANGELOG.md for details.

Changelog

Sourced from vite's changelog.

8.2.2 (2026-08-20)

Features

deps: widen @vitejs/devtools peer range to v0.5.0 (#23302) (495d9ff)

Bug Fixes

bundled-dev: handle lazy request error (#23291) (3ba026d)

bundled-dev: hot update through circular imports instead of reloading (#23259) (3dbddef)

config: resolve sourcemap paths against sourcemap location (#23239) (05a003e)

css: don't pass empty targets to lightningcss (#23295) (2804636)

define: fix match escaped dots to support $-prefixed define keys (#23249) (dcf88bd)

deps: update all non-major dependencies (#23217) (ba958bd)

deps: update rolldown-related dependencies (#23218) (83ecb2c)

module-runner: exclude completed modules from in-flight cycle detection (fix #22999) (#23009) (d9b10a9)

optimizer: close custom extension analysis bundles (#23207) (8fb7675)

reduce Windows 8.3-short-name detection false-positives (#23066) (02cffa9)

respect resolve.preserveSymlinks when resolving root (fix #23197) (#23198) (8413052)

ssr: rewrite computed key of destructing parameter (#23307) (9db0b61)

vite: update outdated upstream file links in license comments (#23285) (c0f2fc6)

Documentation

build: note cssTarget precedence (#23200) (a20a35e)

Miscellaneous Chores

fix ts errors in build test cases (#23209) (a0cfcf7)

Code Refactoring

use JSON import attributes instead of readFileSync in constants (#23258) (1d9fa39)

use named regex constants over inline literals (#22964) (5c1c6c6)

Tests

define: close rolldown bundler after generate (#23231) (b4d66fe)

module-runner: add TLA circular import case (#23299) (4a261f2)

module-runner: simplify server-hmr tests (#23300) (599b44b)

ssr: add destructing assignment case for moduleRunnerTransform (#23308) (cb77e2a)

Build System

use JSON import attributes instead of readFIleSync in rolldown configs (#23251) (d615bcd)

8.2.1 (2026-08-06)

Bug Fixes

build: make client chunkImportMap work with sharedPlugins: true (#23184) (15f0307)

bundled-dev: inject client script tag before chunk scripts (#23161) (eac0cc8)

... (truncated)

Commits

de1111a release: v8.2.2
cb77e2a test(ssr): add destructing assignment case for moduleRunnerTransform (#23308)
9db0b61 fix(ssr): rewrite computed key of destructing parameter (#23307)
8413052 fix: respect resolve.preserveSymlinks when resolving root (fix #23197) (#23...
05a003e fix(config): resolve sourcemap paths against sourcemap location (#23239)
495d9ff feat(deps): widen @vitejs/devtools peer range to v0.5.0 (#23302)
1d9fa39 refactor: use JSON import attributes instead of readFileSync in constants (#2...
2804636 fix(css): don't pass empty targets to lightningcss (#23295)
599b44b test(module-runner): simplify server-hmr tests (#23300)
4a261f2 test(module-runner): add TLA circular import case (#23299)
Additional commits viewable in compare view

Updates wrangler from 4.123.0 to 4.125.0

Release notes

Sourced from wrangler's releases.

wrangler@4.125.0

Minor Changes
#14995 59872c4 Thanks @ThomasRubini! - Add connect trigger for raw sockets

You can now configure a Worker to receive raw socket connections during wrangler dev, delivered directly to the Worker's connect(socket, env, ctx) handler:
{
  "connect": [{ "protocol": "tcp", "port": 5432 }]
}
Each entry opens a listening socket on 127.0.0.1 (or the given address) that forwards incoming connections straight to the Worker, bypassing the local dev HTTP entry point. This requires the experimental compatibility flag. Only "tcp" is supported at the moment.

@cloudflare/config also supports declaring this trigger via triggers.connect(...), which lowers to the connect field above:
import { defineWorker, triggers } from "@cloudflare/config";
export default defineWorker({
triggers: [
triggers.connect({ protocol: "tcp", port: 5432, address: "127.0.0.1" }),
],
});
#15172 c68f9cb Thanks @WillTaylorDev! - Add container support to worker previews

Worker previews now support containers through a new previews.containers configuration block. Container configuration doesn't inherit, so declare containers explicitly in the previews block to enable them for previews. This mirrors how previews.durable_objects works today. Wrangler names each preview container application {worker_name}_{preview_slug}_{class_name}, normalising and shortening the result to what the API accepts. Either change appends a short digest of the composed name, so two names that would otherwise land on one stay distinct. An entry cannot set its own name, because application names are unique to an account and a fixed name would collide between two previews of the same Worker. A Durable Object class is backed by at most one container application, so the validator rejects two entries that share a class_name. Wrangler skips container applications bound to Durable Object classes that another Worker implements through script_name, because the implementing Worker owns its own container application. A binding is not required: a Durable Object declared through migrations or exports and reached only over ctx.exports can still back a container. Every entry must set class_name. A previews.containers entry whose class_name matches no Durable Object class at all is rejected before the preview deployment is created, so a typo fails loudly instead of producing a preview with no container.

Wrangler creates the container applications on wrangler preview. Deleting a preview tears them down server side, so wrangler preview delete doesn't remove them.

Container build and deploy progress prints to stdout. wrangler preview --json suppresses wrangler's own output so it doesn't interleave with the payload, and warnings and errors still go to stderr. Docker's build output and the progress spinner write to stdout directly and bypass that suppression, so parse --json from a non interactive shell, where the spinner is skipped, and prefer a prebuilt image over a Dockerfile.

#15174 649f667 Thanks @WillTaylorDev! - [private beta]: Create the parent Worker automatically when wrangler preview targets one that doesn't exist yet

Previews hang off a parent Worker, so running wrangler preview before the Worker had ever been deployed failed with a raw API error naming the Preview endpoint. Wrangler now offers to create an empty parent Worker and then carries on creating the Preview. The parent uses the same workers.dev and Preview URL settings that wrangler deploy would resolve, without applying routes or cron triggers. In non-interactive environments, Wrangler creates the Worker without asking.

#14735 30c2d47 Thanks @vaishnav-mk! - Add individual and batch Workflow instance deletion to the runtime and SDK.

WorkflowInstance.delete() deletes one instance. Self-deletion stops the current execution.

env.MY_WORKFLOW.deleteBatch(instanceIds) deletes up to 100 instances and returns { deleted, errors } per input position.

wrangler workflows instances delete <name> [id..] deletes instances remotely or with --local; IDs can also come from a JSON array passed with --filename, with a combined limit of 100.
Patch Changes

#15260 5ae9d5b Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"

The following dependency versions have been updated:

... (truncated)

Commits

38b4623 Version Packages (#15250)
39dcea6 move writeOutput into deploy helpers (#15284)
4cdfebd [wrangler] Skip VPC Service remote binding test (#15281)
f2437e6 [workers-auth] Use again the temporary account from the same command run (#15...
c68f9cb feat(wrangler): add container support to worker previews (#15172)
bfcc442 [vitest-plugin] Rename package for v1 (#15074)
30c2d47 [workflows] add individual and batch instance deletion (#14735)
630048b Move a few more bits of triggers deploy into deploy-helpers (#15253)
649f667 WC-5764 Create parent Worker for Previews (#15174)
59872c4 [wrangler] add connect wrangler config section (#14995)
Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR
@dependabot recreate will recreate this PR, overwriting any edits that have been made to it
@dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
@dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
@dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
@dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
@dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
@dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

…ry with 4 updates Bumps the cloudflare-toolchain group with 4 updates in the / directory: [@cloudflare/vite-plugin](https://github.com/cloudflare/workers-sdk/tree/HEAD/packages/vite-plugin-cloudflare), [vinext](https://github.com/cloudflare/vinext), [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) and [wrangler](https://github.com/cloudflare/workers-sdk/tree/HEAD/packages/wrangler). Updates `@cloudflare/vite-plugin` from 1.52.1 to 1.53.1 - [Release notes](https://github.com/cloudflare/workers-sdk/releases) - [Changelog](https://github.com/cloudflare/workers-sdk/blob/main/packages/vite-plugin-cloudflare/CHANGELOG.md) - [Commits](https://github.com/cloudflare/workers-sdk/commits/@cloudflare/vite-plugin@1.53.1/packages/vite-plugin-cloudflare) Updates `vinext` from 1.0.0-beta.6 to 1.0.0-beta.8 - [Release notes](https://github.com/cloudflare/vinext/releases) - [Commits](https://github.com/cloudflare/vinext/compare/vinext@1.0.0-beta.6...vinext@1.0.0-beta.8) Updates `vite` from 8.1.5 to 8.2.2 - [Release notes](https://github.com/vitejs/vite/releases) - [Changelog](https://github.com/vitejs/vite/blob/main/packages/vite/CHANGELOG.md) - [Commits](https://github.com/vitejs/vite/commits/v8.2.2/packages/vite) Updates `wrangler` from 4.123.0 to 4.125.0 - [Release notes](https://github.com/cloudflare/workers-sdk/releases) - [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.125.0/packages/wrangler) --- updated-dependencies: - dependency-name: "@cloudflare/vite-plugin" dependency-version: 1.53.1 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: cloudflare-toolchain - dependency-name: vinext dependency-version: 1.0.0-beta.8 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: cloudflare-toolchain - dependency-name: vite dependency-version: 8.2.2 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: cloudflare-toolchain - dependency-name: wrangler dependency-version: 4.125.0 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: cloudflare-toolchain ... Signed-off-by: dependabot[bot] <support@github.com>

dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Aug 24, 2026

Navigation Menu

build(deps-dev): bump the cloudflare-toolchain group across 1 directory with 4 updates - #37

build(deps-dev): bump the cloudflare-toolchain group across 1 directory with 4 updates#37
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/cloudflare-toolchain-6233c1ea3f

dependabot Bot commented on behalf of github Aug 24, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Conversation

dependabot Bot commented on behalf of github Aug 24, 2026

@​cloudflare/vite-plugin@​1.53.1

Patch Changes

@​cloudflare/vite-plugin@​1.53.0

Minor Changes

Patch Changes

1.53.1

Patch Changes

1.53.0

Minor Changes

Patch Changes

vinext@1.0.0-beta.8

Features

Bug Fixes

Contributors

vinext@1.0.0-beta.7

Bug Fixes

App Router

Build

Misc

Contributors

plugin-legacy@8.2.2

v8.2.2

plugin-legacy@8.2.1

v8.2.1

create-vite@8.2.0

plugin-legacy@8.2.0

v8.2.0

v8.2.0-beta.0

8.2.2 (2026-08-20)

Features

Bug Fixes

Documentation

Miscellaneous Chores

Code Refactoring

Tests

Build System

8.2.1 (2026-08-06)

Bug Fixes

wrangler@4.125.0

Minor Changes

Patch Changes

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

`@cloudflare/vite-plugin@1`.53.1

`@cloudflare/vite-plugin@1`.53.0