Skip to content

fix(deps): update all non-major dependencies - #103

Merged
wgordon17 merged 1 commit into
mainfrom
renovate/all-non-major-dependencies
Jul 24, 2026
Merged

fix(deps): update all non-major dependencies#103
wgordon17 merged 1 commit into
mainfrom
renovate/all-non-major-dependencies

Conversation

@khepri-bot

@khepri-bot khepri-bot Bot commented May 4, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence Type Update Pending
@cloudflare/vite-plugin (source) 1.32.3 → 1.44.0 age confidence devDependencies minor 1.47.0 (+3)
@cloudflare/vitest-pool-workers (source) 0.14.7 → 0.18.4 age confidence devDependencies minor 0.18.8 (+3)
@fast-check/vitest (source) 0.4.0 → 0.4.1 age confidence devDependencies patch
@kobalte/core (source) 0.13.11 → 0.13.12 age confidence dependencies patch
@playwright/test (source) 1.59.1 → 1.61.1 age confidence devDependencies minor
@sentry/cloudflare (source) 10.49.0 → 10.65.0 age confidence dependencies minor 10.68.0 (+2)
@sentry/solid (source) 10.49.0 → 10.65.0 age confidence dependencies minor 10.68.0 (+2)
@tailwindcss/vite (source) 4.2.2 → 4.3.2 age confidence devDependencies minor 4.3.3
actions/checkout (changelog) de0fac2 → d23441a action digest
actions/checkout v6 → v6 age confidence action pin
actions/setup-node (changelog) 48b55a0 → 2499707 action digest
actions/setup-node v6 → v6 age confidence action pin
daisyui (source) 5.5.19 → 5.6.16 age confidence devDependencies minor 5.7.0 (+6)
happy-dom 20.9.0 → 20.10.6 age confidence devDependencies minor 20.11.1 (+1)
node 24.15.0 → 24.18.0 age confidence uses-with minor
solid-js (source) 1.9.12 → 1.9.14 age confidence dependencies patch
tailwindcss (source) 4.2.2 → 4.3.2 age confidence devDependencies minor 4.3.3
tsx (source) 4.21.0 → 4.23.0 age confidence devDependencies minor 4.23.1
vitest (source) 4.1.4 → 4.1.10 age confidence devDependencies patch
vitest (source) 4.1.0 → 4.1.10 age confidence devDependencies patch
wrangler (source) 4.83.0 → 4.110.0 age confidence devDependencies minor 4.114.0 (+3)
zod (source) 4.3.6 → 4.4.3 age confidence dependencies minor

Release Notes

cloudflare/workers-sdk (@​cloudflare/vite-plugin)

v1.44.0

Compare Source

Minor Changes

  • #​14535 1b965c5 Thanks @​Naapperas! - Support dynamic retry delays for Workflow steps in local dev

    A step's retries.delay can now be a function that computes the delay per failed attempt, in addition to a static duration. The function receives { ctx, error } and returns a delay (a number of milliseconds or a duration string like "30 seconds"), and its result is fed into the configured backoff.

    await step.do(
  "call flaky API",
  {
    retries: {
      limit: 5,
      backoff: "constant",
      delay: ({ ctx }) => ctx.attempt * 1000,
    },
  },
  async () => {
    /* ... */
  }
);

    The function is invoked once per failed attempt with a 5 second timeout. If it throws, times out, or returns an invalid value, the step fails without further retries.

Patch Changes

v1.43.3

Compare Source

Patch Changes

v1.43.2

Compare Source

Patch Changes

v1.43.1

Compare Source

Patch Changes

v1.43.0

Compare Source

Minor Changes

  • #​14382 fd92d56 Thanks @​petebacondarwin! - Add support for declarative Durable Object exports

    wrangler deploy now accepts an exports map in wrangler.json as a declarative alternative to the legacy migrations array.

    Each entry in exports is keyed by Durable Object class name. type carries the export kind (currently always "durable-object"); the state field carries the lifecycle and defaults to "created" (live) when omitted:

    {
  "exports": {
    // Provision a new Durable Object class (`MyDO`)
    "MyDO": { "type": "durable-object", "storage": "sqlite" },
    // Delete Durable Object class (`OldGone`)
    "OldGone": { "type": "durable-object", "state": "deleted" },
    // Rename a Durable Object class (from `OldName` to `NewName`)
    "OldName": {
      "type": "durable-object",
      "state": "renamed",
      "renamed_to": "NewName"
    },
    "NewName": { "type": "durable-object", "storage": "sqlite" },
    // Transfer a Durable Object (`Outgoing`) to a new Worker (`target-worker`)
    "Outgoing": {
      "type": "durable-object",
      "state": "transferred",
      "transferred_to": "target-worker"
    },
    // Prepare to receive the transfer of a Durable Object (`Incoming`) from another Worker (`source-worker`)
    "Incoming": {
      "type": "durable-object",
      "state": "expecting-transfer",
      "storage": "sqlite",
      "transfer_from": "source-worker"
    }
  }
}

    When a Worker declares Durable Object class bindings but no lifecycle for them (neither a migrations array nor an exports map), wrangler warns and now suggests a declarative exports entry for each class (previously it suggested a legacy migrations block).

    The deployment response now surfaces the server's reconciliation result — created namespaces, applied tombstones, structured per-scenario info entries, and a removable_entries hint for stale tombstones that are safe to delete from the config. Blocking errors return the structured per-class detail with scenario tags, suggested remediation, and any referencing-script context.

    wrangler versions upload also forwards exports. Declarative exports lifecycle changes are reconciled when the version is deployed (wrangler versions deploy or wrangler deploy), so a versions upload payload can declare new classes in exports without immediately provisioning them. An actor binding (durable_objects.bindings) to a class declared only in exports on the same versions upload is rejected with a clear error (code 100406) — the binding cannot be resolved until the namespace is provisioned. Either stage the new class via ctx.exports.X (no binding required) on versions upload and add the binding at deploy time, or use wrangler deploy to provision and bind in one step (the same constraint applies to the migrations flow).

    Multi-version deploys (wrangler versions deploy A@50% B@50%) where the selected versions disagree on declarative exports are rejected server-side with a clear message: deploy the version that changes exports at 100% first, then run the percentage-split deploy. This prevents traffic on one branch routing to code that references unprovisioned or just-deleted DO namespaces. Single-version (100%) deploys are unaffected.

    Local development (wrangler dev, vite dev and unstable_startWorker) reads Durable Object SQLite storage settings from the new exports field, so applications using the declarative flow get correct local-dev storage without needing to also declare a migrations block.

    @cloudflare/vitest-pool-workers also picks up Durable Object configuration from exports, so tests against an exports-only Worker run with the correct local SQLite storage and can reach unbound Durable Object classes via ctx.exports.X.

    wrangler types is also aware of exports. Live entries (including expecting-transfer, the receiving side of a two-phase transfer) are added to Cloudflare.GlobalProps.durableNamespaces, which types ctx.exports.X for unbound Durable Objects declared only via exports.

Patch Changes

v1.42.4

Compare Source

Patch Changes

v1.42.3

Compare Source

Patch Changes

v1.42.2

Compare Source

Patch Changes

  • #​14358 4ef872f Thanks @​gabivlj! - Fix container egress interception on arm64 Docker runtimes

    Both wrangler dev and the Cloudflare Vite plugin no longer force the proxy-everything sidecar image to pull as linux/amd64, allowing Docker to select the native image from the multi-platform manifest. Set MINIFLARE_CONTAINER_EGRESS_IMAGE_PLATFORM to force a specific platform when needed.

  • Updated dependencies [a085dec, 9a0de8f, fab565f, 3f02864, 4ef872f, 2a02858, e312dec]:

    • miniflare@​4.20260623.0
    • wrangler@​4.104.0

v1.42.1

Compare Source

Patch Changes

  • #​14366 c6579d3 Thanks @​jamesopstad! - Resolve relative cf-worker entrypoint imports relative to the importing module

    When loading the experimental cloudflare.config.ts, a relative entrypoint imported with import ... with { type: "cf-worker" } (e.g. ./src/index.ts) is now anchored to the module where the import is written, rather than being passed through verbatim and later resolved against the top-level config file. This fixes incorrect resolution when the import lives in a file other than the entry config — for example a config that re-exports from a nested file.

    Bare specifiers (such as @scope/pkg) and virtual modules (such as virtual:foo) are still left unresolved so that consumers can apply their own resolution.

  • Updated dependencies [c6579d3, 444b75e, b38823f, cfd6205, cfd6205]:

    • wrangler@​4.103.0
    • miniflare@​4.20260617.1

v1.42.0

Compare Source

Minor Changes

  • #​14339 aa49856 Thanks @​jamesopstad! - Add a build command to the experimental, internal cf-vite delegate binary

    cf-vite build runs Vite's full multi-environment app build (via the Builder API) and enables the experimental Build Output API by default, emitting a self-contained .cloudflare/output/v0/ directory. It forces experimental.newConfig and experimental.newConfig.cfBuildOutput on, so a cloudflare.config.ts is required at the project root.

Patch Changes

  • #​14346 e930bd4 Thanks @​haidargit! - Bump ws from 8.20.1 to 8.21.0 to address GHSA-96hv-2xvq-fx4p

    GHSA-96hv-2xvq-fx4p / CVE-2026-48779 (high severity) reports a remote memory-exhaustion DoS in ws@<8.21.0: a peer sending a high volume of tiny fragments and data chunks over modest network traffic can crash a ws server or client via OOM. The fix shipped in ws@8.21.0 (commit 2b2abd45, released 2026-05-22), which also introduces the maxBufferedChunks and maxFragments options. This change bumps the workspace catalog entry so that miniflare, wrangler, and @cloudflare/vite-plugin all pick up the patched release.

  • #​14351 6c7df19 Thanks @​jamesopstad! - Force the experimental new config on by default in the cf-vite dev delegate

  • #​14218 4eed569 Thanks @​matingathani! - Allow resolve.external containing only Node.js built-ins in Worker environments

    Vitest 4 automatically sets resolve.external to the full list of Node.js built-in modules for non-standard Vite environments via its internal runnerTransform plugin. Previously, the Cloudflare Vite plugin rejected any non-empty resolve.external array, throwing an incompatibility error on startup when used alongside Vitest 4.

    The validation check now allows resolve.external arrays that contain only Node.js built-in module names (both bare fs and node:fs forms). The error is only thrown when resolve.external is true or contains non-built-in package names that would prevent user code from being bundled into the Worker.

  • Updated dependencies [673b09e, e930bd4, f6e49dd, 5c3bb11, 296ad65, 594544d, a79b899, 5dfb788, ca61558, 36777db]:

    • miniflare@​4.20260617.0
    • wrangler@​4.102.0

v1.41.0

Compare Source

Minor Changes

  • #​14279 e6e4b07 Thanks @​jamesopstad! - Add experimental.newConfig.cfBuildOutput option to support future deployments via the cf CLI

    // vite.config.ts
import { defineConfig } from "vite";
import { cloudflare } from "@&#8203;cloudflare/vite-plugin";

export default defineConfig({
  plugins: [
    cloudflare({
      experimental: {
        newConfig: {
          cfBuildOutput: true,
        },
      },
    }),
  ],
});
Patch Changes

v1.40.2

Compare Source

Patch Changes

  • #​14184 e305126 Thanks @​penalosa! - Drop the --config flag from the experimental internal cf-vite delegate binary.

    The wrangler config file is now discovered by cloudflare() itself rather than being passed through, keeping cf-vite's flag surface (--mode, --port, --host, --local) in sync with the sibling cf-wrangler delegate. cf-vite is an internal integration point spawned by Cloudflare tooling and is not intended to be run directly by users.

  • Updated dependencies [98c9afe, e305126, f3990b2, 4597f08, 25722ac, 41f75c0, 10b5538, 818c105, 2ae6099, 2047a32, 2047a32, e8561c2]:

    • wrangler@​4.100.0
    • miniflare@​4.20260611.0

v1.40.1

Compare Source

Patch Changes

v1.40.0

Compare Source

Minor Changes

  • #​14013 3cf9d0e Thanks @​jamesopstad! - Add experimental experimental.newConfig option to load the entry Worker's configuration from cloudflare.config.ts

    This is an experimental, opt-in feature. When enabled, the plugin loads the entry Worker's configuration from a cloudflare.config.ts file instead of the usual wrangler.json / wrangler.jsonc / wrangler.toml.

    Pass true to enable with defaults, or an object to customise behaviour. Currently the only sub-option is types.generate (defaults to true), which writes a worker-configuration.d.ts file next to the config. This enables typed env and exports for your Worker and currently assumes that you have @cloudflare/workers-types installed.

    // vite.config.ts
import { defineConfig } from "vite";
import { cloudflare } from "@&#8203;cloudflare/vite-plugin";

export default defineConfig({
  plugins: [
    cloudflare({
      experimental: {
        newConfig: true,
      },
    }),
  ],
});
    // cloudflare.config.ts
import {
	defineWorker,
	bindings,
} from "@&#8203;cloudflare/vite-plugin/experimental-config";
import * as entrypoint from "./src/index.ts" with { type: "cf-worker" };

export default defineWorker((ctx) => ({
	name: "my-worker",
	entrypoint,
	compatibilityDate: "2026-05-18",
	env: {
		MY_TEXT: bindings.text(`The mode is ${ctx.mode}`),
		MY_KV: bindings.kv(),
	},
}));

    A few limitations apply while the feature is experimental:

    • configPath cannot be combined with experimental.newConfig. The entry Worker is always loaded from cloudflare.config.ts at the project root.
    • auxiliaryWorkers are not yet supported with experimental.newConfig.

    Because this is experimental, the option, the cloudflare.config.ts schema, and the @cloudflare/vite-plugin/experimental-config exports may change in any release.

Patch Changes

v1.39.2

Compare Source

Patch Changes

  • #​13893 d8a16e7 Thanks @​penalosa! - Add an experimental, internal cf-vite delegate binary

    This adds an experimental bin/cf-vite binary that is spawned by Cloudflare's own parent tooling to drive the plugin as a long-running dev-server subprocess. It is not part of the plugin's public API surface, is not intended to be invoked directly, and its contract may change at any time without notice.

  • #​14117 3c86121 Thanks @​aicayzer! - Forward response headers from the Worker on WebSocket upgrade responses

    Headers set on a new Response(null, { status: 101, webSocket, headers }) returned from the Worker are now propagated to the upgrade response sent to the browser during vite dev. Previously the headers were dropped, so cookies (Set-Cookie) and custom headers (X-*) on WebSocket handshake responses were invisible client-side — even though they were delivered correctly by wrangler dev.

  • Updated dependencies [b210c5e, aec1bb8, e06cbb7, 9a26191, 5565823, 4ef790b, 890fca7, 6fc9777, 337e912, 8e7b74f, e86489a, 42288d4, 65b5f9e, 3a746ac, 64ef9fd, 94b29f7]:

    • wrangler@​4.97.0
    • miniflare@​4.20260601.0

v1.39.1

Compare Source

Patch Changes

v1.39.0

Compare Source

Minor Changes

  • #​13985 c809d30 Thanks @​jamesopstad! - Add assetsOnly (entry Worker) and devOnly (auxiliary Workers) options to the plugin config

    Both options accept a boolean or a function that returns a boolean. The function is evaluated lazily at build time, allowing frameworks to provide the value after initialization.

    Use assetsOnly on the entry Worker to skip building the Worker and instead emit an assets-only Wrangler config to the client output directory. This enables frameworks such as Astro to use the ssr environment during development but produce a fully static app for deployment.

    export default defineConfig({
  plugins: [
    cloudflare({
      assetsOnly: () => isStaticBuild,
    }),
  ],
});

    Use devOnly on an auxiliary Worker to include it during vite dev but skip it at build time.

    export default defineConfig({
  plugins: [
    cloudflare({
      auxiliaryWorkers: [
        { configPath: "./dev-only-worker/wrangler.jsonc", devOnly: true },
      ],
    }),
  ],
});
Patch Changes

v1.38.0

Compare Source

Minor Changes

  • #​13989 f598eac Thanks @​MattieTK! - Print a QR code alongside the tunnel URL when sharing via Cloudflare Tunnel

    When a tunnel is started (via wrangler dev --tunnel or the Vite plugin with tunnel: true), a scannable QR code is now printed to the terminal beneath the tunnel URL. This makes it easy to open the tunnel on a mobile device without manually copying the URL.

    The QR code uses Unicode block characters for a compact representation and is gen

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (in timezone America/New_York)

  • Branch creation
    • Between 12:00 AM and 08:59 AM, only on Monday (* 0-8 * * 1)
  • 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate.

@khepri-bot khepri-bot Bot added the renovate label May 4, 2026
@khepri-bot
khepri-bot Bot force-pushed the renovate/all-non-major-dependencies branch 6 times, most recently from cf02552 to 3dc5465 Compare May 7, 2026 14:05
@khepri-bot khepri-bot Bot changed the title chore(deps): update all non-major dependencies fix(deps): update all non-major dependencies May 7, 2026
@khepri-bot
khepri-bot Bot force-pushed the renovate/all-non-major-dependencies branch 7 times, most recently from 687557d to ba9f052 Compare May 14, 2026 17:03
@khepri-bot
khepri-bot Bot force-pushed the renovate/all-non-major-dependencies branch 7 times, most recently from da802e8 to 7df6a9a Compare July 23, 2026 19:39
@khepri-bot
khepri-bot Bot force-pushed the renovate/all-non-major-dependencies branch from 7df6a9a to fd1d10a Compare July 24, 2026 11:14
@wgordon17
wgordon17 merged commit e7f3bd4 into main Jul 24, 2026
1 check passed
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

renovate

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@wgordon17