Files
wehub-resource-sync 70bf21e064
Deploy (to testing) and Test Playground Preview Worker / Deploy Playground Preview Worker (testing) (push) Has been skipped
Deploy Workers Shared Staging / Deploy Workers Shared Staging (push) Failing after 0s
Prerelease / build (push) Has been skipped
Handle Changesets / Handle Changesets (push) Has been cancelled
Semgrep OSS scan / semgrep-oss (push) Has been cancelled
chore: import upstream snapshot with attribution
2026-07-13 12:30:11 +08:00

13 KiB

@cloudflare/deploy-helpers

0.4.0

Minor Changes

  • #14591 0283a1f Thanks @dario-piotrowicz! - Export collectPackageDependencies for npm dependency metadata collection

    The package dependency discovery logic (collecting installed npm package names and versions from a project's package.json) is now owned by deploy-helpers and called internally during deploy and version uploads, rather than being pre-computed in wrangler and passed through as a prop.

Patch Changes

0.3.3

Patch Changes

0.3.2

Patch Changes

0.3.1

Patch Changes

0.3.0

Minor Changes

  • #14474 aa5d580 Thanks @WillTaylorDev! - Add cache options for WorkerEntrypoint exports

    You can now set cache options on WorkerEntrypoint exports and configure cross-version cache behavior globally:

    // wrangler.json
    {
      "cache": { "enabled": true, "cross_version_cache": true },
      "exports": {
        "default": {
          "type": "worker",
          "cache": { "enabled": false }
        },
        "Admin": {
          "type": "worker",
          "cache": { "enabled": true }
        }
      }
    }
    

    Wrangler sends the exports config to the deploy and version upload APIs alongside the global cache.enabled and cache.cross_version_cache settings. The platform resolves those global settings plus cache overrides on exports and validates which entrypoint names are cacheable.

Patch Changes

  • #14305 98793d8 Thanks @jbwcloudflare! - Improve asset upload performance with single-file uploads

    Asset uploads now use a more efficient per-file upload path when the platform enables it. This is rolled out server-side and requires no configuration changes. Existing upload behavior is unchanged when the new path is not enabled.

  • Updated dependencies [aa5d580, 6b0ce98]:

0.2.5

Patch Changes

0.2.4

Patch Changes

0.2.3

Patch Changes

0.2.2

Patch Changes

0.2.1

Patch Changes

  • #14347 673b09e Thanks @jamesopstad! - Update undici from 7.24.8 to 7.28.0

  • #14340 f6e49dd Thanks @emily-shen! - add skipLastDeployedFromApiCheck to override deploy source check

  • #14269 5dfb788 Thanks @mattjohnsonpint! - Support dev.plugin on typed services bindings

    Wrangler only honored dev.plugin on unsafe.bindings entries, so users authoring a service binding via services[] could not wire it to a local Miniflare plugin during wrangler dev — they had to fall back to unsafe.bindings and accept a "directly supported by wrangler" warning. Typed services bindings now accept the same dev: { plugin, options? } shape, route the binding through Miniflare's external-plugin pathway in wrangler dev, and strip the field at deploy time. Validation rejects malformed dev shapes.

  • Updated dependencies [673b09e, e930bd4, 5c3bb11, 296ad65, 5dfb788]:

0.2.0

Minor Changes

  • #14321 88662aa Thanks @emily-shen! - re-export OutputWorkerSchema from internal config package

  • #14265 e3fce14 Thanks @emily-shen! - Expose Cloudflare config conversion utilities from deploy helpers

    @cloudflare/deploy-helpers now re-exports ConfigSchema and convertToWranglerConfig from the internal @cloudflare/config package, so consumers can parse and convert Cloudflare config files without depending on the unpublished package directly.

Patch Changes

  • #14265 e3fce14 Thanks @emily-shen! - Bundle private internal dependencies in deploy helpers

    @cloudflare/deploy-helpers no longer declares private workspace packages as runtime dependencies, so installing the package from npm does not require unpublished internal packages.

  • #14304 ee82c76 Thanks @emily-shen! - Skip resource provisioning for asset-only deployments

    Previously, asset-only deployments would provision resources even when there was no user Worker script. On a subsequent deploy, we would re-attempt provisioning as the previous asset-only upload would/could not be bound to the previously provisioned resource. Provisioning would then error as the resource had already been created, blocking the deploy.

  • Updated dependencies [0e055d3, 27db82c, 2a6a26b, 9a424ed, ecfdd5a, 41f391f]:

0.1.3

Patch Changes

0.1.2

Patch Changes

0.1.1

Patch Changes

  • #14063 65b5f9e Thanks @emily-shen! - Move fetch helpers into @cloudflare/workers-utils

    Shared Cloudflare API fetch helper types and plumbing now live in @cloudflare/workers-utils so Wrangler and other clients can use the same implementation.

0.1.0

Minor Changes

  • #14014 d042705 Thanks @emily-shen! - Add @cloudflare/deploy-helpers package.

    This introduces a shared internal package for deploy-related helper types and code.