Wrangler Changelog

2024-06-04

3.59.0

#5963 bf803d7 Thanks @Skye-31! - Feature: Add support for hiding the "unsafe" fields are experimental warning using an environment variable
By setting WRANGLER_DISABLE_EXPERIMENTAL_WARNING to any truthy value, these warnings will be hidden.
Updated dependencies [ bdbb7f8]:
- miniflare@3.20240524.2

2024-05-31

3.58.0

#5933 93b98cb Thanks @WalshyDev! - feature: allow for writing authentication details per API environment. This allows someone targetting staging to have their staging auth details saved separately from production, this saves them logging in and out when switching environments.
#5938 9e4d8bc Thanks @threepointone! - fix: let “assets” in wrangler.toml be a string
The experimental “assets” field can be either a string or an object. However the type definition marks it only as an object. This is a problem because we use this to generate the json schema, which gets picked up by vscode’s even better toml extension, and shows it to be an error when used with a string (even though it works fine). The fix is to simply change the type definition to add a string variant.
#5758 8e5e589 Thanks @Jackenmen! - fix: use correct type for AI binding instead of unknown
Updated dependencies [ e0e7725]:
- miniflare@3.20240524.1

2024-05-28

3.57.2

#5905 53f22a0 Thanks @penalosa! - fix: Remove WARP certificate injection. Instead, you should ensure that any custom certificates that are needed are included in NODE_EXTRA_CA_CERTS.
#5930 57daae0 Thanks @WalshyDev! - chore: improve error message when updating secret for a non-deployed latest version.
#5703 a905f31 Thanks @penalosa! - fix: Don’t use ExportedHandler["middleware"] for injecting middleware
Updated dependencies [ 64ccdd6, 4458a9e]:
- miniflare@3.20240524.0

2024-05-21

3.57.1

#5859 f2ceb3a Thanks @w-kuhn! - fix: queue consumer max_batch_timeout should accept a 0 value
#5862 441a05f Thanks @CarmenPopoviciu! - fix: wrangler pages deploy should fail if deployment was unsuccessful
If a Pages project fails to deploy, wrangler pages deploy will log an error message, but exit successfully. It should instead throw a FatalError.
#5812 d5e00e4 Thanks @thomasgauvin! - fix: remove Hyperdrive warning for local development.
Hyperdrive bindings are now supported when developing locally with Hyperdrive. We should update our logs to reflect this.
#5626 a12b031 Thanks @RamIdeas! - chore: ignore workerd output (error: CODE_MOVED) not intended for end-user devs

2024-05-17

3.57.0

#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
#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.

2024-05-14

3.56.0

#5712 151bc3d Thanks @penalosa! - feat: Support mtls_certificates and browser bindings when using wrangler.toml with a Pages project
#5813 9627cef Thanks @GregBrimble! - fix: Upload Pages project assets with more grace
- Reduces the maximum bucket size from 50 MiB to 40 MiB.
- Reduces the maximum asset count from 5000 to 2000.
- Allows for more retries (with increased sleep between attempts) when encountering an API gateway failure.
Updated dependencies [ 0725f6f, 89b6d7f]:
- miniflare@3.20240512.0

Wrangler Changelog

​​ 2024-06-04

​​ 3.59.0

​​ 2024-05-31

​​ 3.58.0

​​ 2024-05-28

​​ 3.57.2

​​ 2024-05-21

​​ 3.57.1

​​ 2024-05-17

​​ 3.57.0

​​ 2024-05-14

​​ 3.56.0

2024-06-04

3.59.0

2024-05-31

3.58.0

2024-05-28

3.57.2

2024-05-21

3.57.1

2024-05-17

3.57.0

2024-05-14

3.56.0