Version Packages

[workers-devprod]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

[email protected]

Minor Changes

• #5696 7e97ba8 Thanks @geelen! - feature: Improved d1 execute --file --remote performance & added support for much larger SQL files within a single transaction.

• #5819 63f7acb Thanks @CarmenPopoviciu! - fix: Show feedback on Pages project deployment failure

  Today, if uploading a Pages Function, or deploying a Pages project fails for whatever reason, there’s no feedback shown to the user. Worse yet, the shown message is misleading, saying the deployment was successful, when in fact it was not:

  ✨ Deployment complete!
  

  This commit ensures that we provide users with:

  • the correct feedback with respect to their Pages deployment
  • the appropriate messaging depending on the status of their project's deployment status
  • the appropriate logs in case of a deployment failure

• #5814 2869e03 Thanks @CarmenPopoviciu! - fix: Display correct global flags in wrangler pages --help

  Running wrangler pages --help will list, amongst others, the following global flags:

  -j, --experimental-json-config
  -c, --config
  -e, --env
  -h, --help
  -v, --version
  

  This is not accurate, since flags such as --config, --experimental-json-config, or env are not supported by Pages.

  This commit ensures we display the correct global flags that apply to Pages.

• #5818 df2daf2 Thanks @WalshyDev! - chore: Deprecate usage of the deployment object on the unsafe metadata binding in favor of the new version_metadata binding.

  If you're currently using the old binding, please move over to the new version_metadata binding by adding:

  [version_metadata]
  binding = "CF_VERSION_METADATA"

  and updating your usage accordingly. You can find the docs for the new binding here: https://developers.cloudflare.com/workers/runtime-apis/bindings/version-metadata

Patch Changes

• #5838 609debd Thanks @petebacondarwin! - fix: update undici to the latest version to avoid a potential vulnerability

• #5832 86a6e09 Thanks @petebacondarwin! - fix: do not allow non-string values in bulk secret uploads

  Prior to Wrangler 3.4.0 we displayed an error if the user tried to upload a
  JSON file that contained non-string secrets, since these are not supported
  by the Cloudflare backend.

  This change reintroduces that check to give the user a helpful error message
  rather than a cryptic workers.api.error.invalid_script_config error code.

[email protected]

Patch Changes

• #5602 93cd7ae Thanks @dependabot! - chore: update dependencies of "create-cloudflare" package

  The following dependency versions have been updated:

  Dependency	From	To
  gatsby	5.13.3	5.13.4

• #5835 717e13e Thanks @dependabot! - chore: update dependencies of "create-cloudflare" package

  The following dependency versions have been updated:

  Dependency	From	To
  @angular/create	17.2.3	17.3.7

• #5836 b3b4d3a Thanks @dependabot! - chore: update dependencies of "create-cloudflare" package

  The following dependency versions have been updated:

  Dependency	From	To
  create-qwik	1.4.5	1.5.4

• #5547 e6ecf8c Thanks @connorads! - fix: provide a simple fetch handler to the scheduled template to avoid confusing error messages.

  Fixes 🐛 BUG: "scheduled" template broken #4560

• #5855 3a65060 Thanks @petebacondarwin! - chore: bump undici to 5.28.4

@cloudflare/[email protected]

Patch Changes

• #5838 609debd Thanks @petebacondarwin! - fix: update undici to the latest version to avoid a potential vulnerability

• Updated dependencies [7e97ba8, 609debd, 63f7acb, 2869e03, 86a6e09, df2daf2]:

  • [email protected]

[email protected]

Patch Changes

• #5838 609debd Thanks @petebacondarwin! - fix: update undici to the latest version to avoid a potential vulnerability

[email protected]

Patch Changes

• #5838 609debd Thanks @petebacondarwin! - fix: update undici to the latest version to avoid a potential vulnerability

[github-actions]

A wrangler prerelease is available for testing. You can install this latest build in your project with:

npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/9119542223/npm-package-wrangler-5837

You can reference the automatically updated head of this PR with:

npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/prs/5837/npm-package-wrangler-5837

Or you can use npx with this latest build directly:

npx https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/9119542223/npm-package-wrangler-5837 dev path/to/script.js

Additional artifacts:

npx https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/9119542223/npm-package-create-cloudflare-5837 --no-auto-update

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/9119542223/npm-package-cloudflare-kv-asset-handler-5837

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/9119542223/npm-package-miniflare-5837

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/9119542223/npm-package-cloudflare-pages-shared-5837

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/9119542223/npm-package-cloudflare-vitest-pool-workers-5837

Note that these links will no longer work once the GitHub Actions artifact expires.

---

[email protected] includes the following runtime dependencies:

Package	Constraint	Resolved
miniflare	workspace:*	3.20240512.0
workerd	1.20240512.0	1.20240512.0
workerd --version	1.20240512.0	2024-05-12

Please ensure constraints are pinned, and miniflare/workerd minor versions match.