Change8

wrangler@4.51.0

Breaking Changes
📦 cloudflare-workersView on GitHub →
1 breaking2 features🐛 1 fixes🔧 2 symbols

Summary

This release introduces experimental support for autoconfig-powered Astro projects and adds the ability to select deployment environments via the CLOUDFLARE_ENV environment variable, alongside dependency updates and an R2 bulk put rate limit.

⚠️ Breaking Changes

  • If you use `wrangler versions upload` with `--env` and your Worker was built using `@cloudflare/vite-plugin` with a specific environment, Wrangler now checks that the specified environment matches the environment used during the build. If they do not match, the upload will fail to prevent accidental deployment to the wrong environment.

Migration Steps

  1. If you rely on deploying environments built via `@cloudflare/vite-plugin` using `wrangler versions upload`, ensure that any explicit `--env` flag provided to Wrangler matches the environment selected during the build process, or remove the `--env` flag if you intend to use the environment selected during the build.

✨ New Features

  • Enabled experimental support for autoconfig-powered Astro projects.
  • Introduced support for the `CLOUDFLARE_ENV` environment variable to select the active environment for commands like `wrangler versions upload`. The `--env` command line argument still takes precedence.

🐛 Bug Fixes

  • Rate limit applied to R2 bulk put operations.

🔧 Affected Symbols

wrangler versions upload@cloudflare/vite-plugin