Skip to content

Releases: cloudflare/workers-sdk

wrangler@4.103.0

19 Jun 13:30
4d8ffcb

Choose a tag to compare

Minor Changes

  • #14295 cfd6205 Thanks @dario-piotrowicz! - Move unstable_getWorkerNameFromProject from wrangler to @cloudflare/workers-utils

    The unstable_getWorkerNameFromProject export has been removed from the wrangler package. This function is now available as getWorkerNameFromProject (without the unstable_ prefix) from @cloudflare/workers-utils. If you were importing this function from wrangler, update your import to use @cloudflare/workers-utils instead.

  • #14295 cfd6205 Thanks @dario-piotrowicz! - Remove experimental autoconfig exports

    The experimental autoconfig exports (experimental_getDetailsForAutoConfig, experimental_runAutoConfig, experimental_AutoConfigFramework) have been removed. This logic has been moved to the @cloudflare/autoconfig package (without the experimental_ prefixes since the package itself is pre-v1).

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.

  • #14316 444b75e Thanks @matingathani! - Prevent wrangler dev crash when source-mapping a truncated error chunk

    When a worker logs many errors in quick succession, the stderr chunks received by wrangler dev can be truncated mid-stack-frame, leaving a call site with an invalid column number. The source map library throws in that case, which was crashing the wrangler process entirely. The error is now caught and the original (un-source-mapped) text is returned instead.

  • #14118 b38823f Thanks @aicayzer! - Fix Uint8Array step outputs in local Workflows being persisted with the full backing ArrayBuffer

    A Uint8Array returned from a Workflows step under wrangler dev was serialised together with its full underlying ArrayBuffer, causing a raw SQLITE_TOOBIG error at view sizes well below the documented 1MiB step-output limit. For example, a 200KB view sliced from an 800KB buffer (a common pattern from crypto.getRandomValues or arr.slice(...) on a larger pool) would fail. The view's bytes are now copied to a tight buffer before persistence, bringing local behaviour in line with production. Fixes #14101.

  • Updated dependencies [b38823f]:

    • miniflare@4.20260617.1

miniflare@4.20260617.1

19 Jun 13:30
4d8ffcb

Choose a tag to compare

Patch Changes

  • #14118 b38823f Thanks @aicayzer! - Fix Uint8Array step outputs in local Workflows being persisted with the full backing ArrayBuffer

    A Uint8Array returned from a Workflows step under wrangler dev was serialised together with its full underlying ArrayBuffer, causing a raw SQLITE_TOOBIG error at view sizes well below the documented 1MiB step-output limit. For example, a 200KB view sliced from an 800KB buffer (a common pattern from crypto.getRandomValues or arr.slice(...) on a larger pool) would fail. The view's bytes are now copied to a tight buffer before persistence, bringing local behaviour in line with production. Fixes #14101.

create-cloudflare@2.70.5

19 Jun 13:30
4d8ffcb

Choose a tag to compare

Patch Changes

  • #14361 df43f59 Thanks @jamesopstad! - Fix infinite loop when running C3 with pnpm 11

    When invoked via pnpm create cloudflare@latest, C3 checks npm for a newer version and re-launches itself with the latest version if one is available. pnpm 11 enables the minimumReleaseAge supply-chain protection by default, so pnpm create cloudflare@latest will not resolve a version published in the last 24 hours. When the npm latest tag points at a version newer than what pnpm is willing to install, the update check stayed true and C3 re-launched itself forever.

    The relaunched process is now marked so it never re-runs the auto-update check, ensuring C3 starts up after at most one relaunch regardless of the package manager's version resolution.

@cloudflare/workers-utils@0.24.0

19 Jun 13:30
4d8ffcb

Choose a tag to compare

Minor Changes

  • #14295 cfd6205 Thanks @dario-piotrowicz! - Move unstable_getWorkerNameFromProject from wrangler to @cloudflare/workers-utils

    The unstable_getWorkerNameFromProject export has been removed from the wrangler package. This function is now available as getWorkerNameFromProject (without the unstable_ prefix) from @cloudflare/workers-utils. If you were importing this function from wrangler, update your import to use @cloudflare/workers-utils instead.

  • #14295 cfd6205 Thanks @dario-piotrowicz! - Add PackageManager type and constants

    Added the PackageManager interface and package manager constants (NpmPackageManager, PnpmPackageManager, YarnPackageManager, BunPackageManager).

@cloudflare/workers-auth@0.3.2

19 Jun 13:30
4d8ffcb

Choose a tag to compare

Patch Changes

  • Updated dependencies [cfd6205, cfd6205]:
    • @cloudflare/workers-utils@0.24.0

@cloudflare/vitest-pool-workers@0.16.18

19 Jun 13:30
4d8ffcb

Choose a tag to compare

Patch Changes

@cloudflare/vite-plugin@1.42.1

19 Jun 13:30
4d8ffcb

Choose a tag to compare

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

@cloudflare/pages-shared@0.13.148

19 Jun 13:30
4d8ffcb

Choose a tag to compare

Patch Changes

  • Updated dependencies [b38823f]:
    • miniflare@4.20260617.1

@cloudflare/deploy-helpers@0.2.2

19 Jun 13:30
4d8ffcb

Choose a tag to compare

Patch Changes

  • #14354 7649895 Thanks @emily-shen! - Move resource provisioning into deploy helpers

    Worker deploy and versions upload now share the deploy helpers implementation for provisioning bindings, reducing Wrangler-specific callback wiring while preserving existing behavior.

  • Updated dependencies [b38823f, cfd6205, cfd6205]:

    • miniflare@4.20260617.1
    • @cloudflare/workers-utils@0.24.0
    • @cloudflare/cli-shared-helpers@0.1.10

@cloudflare/cli-shared-helpers@0.1.10

19 Jun 13:30
4d8ffcb

Choose a tag to compare

Patch Changes

  • Updated dependencies [cfd6205, cfd6205]:
    • @cloudflare/workers-utils@0.24.0