wrangler@4.77.0
Breaking Changes📦 cloudflare-workersView on GitHub →
⚠ 1 breaking✨ 3 features🐛 2 fixes🔧 4 symbols
Summary
This release introduces validation for required secrets during deployment and upload using the experimental `secrets` configuration property. It also improves the reliability of remote development sessions and fixes Qwik scaffolding issues for Workers targets.
⚠️ Breaking Changes
- Removed support for the `cf-requirements` configuration property for Python workers, as it is no longer compatible with the runtime. Users relying on this feature for Python workers must find alternative configuration methods.
Migration Steps
- If you were using Python workers with the `cf-requirements` configuration, remove this configuration as it is no longer supported.
- If using Qwik, ensure you are using the correct `cloudflare-workers` target when scaffolding to avoid Pages-specific configurations.
✨ New Features
- Added validation for the experimental `secrets.required` property during `wrangler versions upload`. Upload fails if required secrets are missing.
- Added validation for the experimental `secrets.required` property during `wrangler deploy`. Deploy fails if required secrets are missing.
- Remote preview sessions (`wrangler dev --remote`) now automatically retry transient 5xx API errors (up to 3 attempts) and enforce a 30-second per-request timeout.
🐛 Bug Fixes
- Fixed Qwik scaffolding to use `qwik add cloudflare-workers` instead of `qwik add cloudflare-pages` for Workers targets, ensuring correct adapter directory structure and configuration files (`wrangler.jsonc` with correct fields, `.assetsignore`, and correct Vite config).
- Added retry and timeout protection to remote preview API calls to prevent indefinite blocking during hung or failed API responses.