Wrangler Changelog
2024-05-17
3.57.0
#5696
7e97ba8
Thanks @geelen! - feature: Improvedd1 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 failureToday, 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 inwrangler 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
, orenv
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 uploadsPrior 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: Supportmtls_certificates
andbrowser
bindings when usingwrangler.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.
2024-05-09
3.55.0
#5570
66bdad0
Thanks @sesteves! - feature: support delayed delivery in the miniflare’s queue simulator.This change updates the miniflare’s queue broker to support delayed delivery of messages, both when sending the message from a producer and when retrying the message from a consumer.
#5740
97741db
Thanks @WalshyDev! - chore: log “Version ID” inwrangler deploy
,wrangler deployments list
,wrangler deployments view
andwrangler rollback
to support migration from the deprecated “Deployment ID”. Users should update any parsing to use “Version ID” before “Deployment ID” is removed.#5754
f673c66
Thanks @RamIdeas! - fix: when using custom builds, thewrangler dev
proxy server was sometimes left in a paused stateThis could be observed as the browser loading indefinitely, after saving a source file (unchanged) when using custom builds. This is now fixed by ensuring the proxy server is unpaused after a short timeout period.
2024-05-02
3.53.1
#5091
6365c90
Thanks @Cherry! - fix: better handle dashes and other invalid JS identifier characters inwrangler types
generation for vars, bindings, etc.Previously, with the following in your
wrangler.toml
, an invalid types file would be generated:[vars]some-var = "foobar"Now, the generated types file will be valid:
interface Env {"some-var": "foobar";}#5748
27966a4
Thanks @penalosa! - fix: Load sourcemaps relative to the entry directory, not cwd.#5746
1dd9f7e
Thanks @petebacondarwin! - fix: suggest trying to update Wrangler if there is a newer one available after an unexpected error#5226
f63e7a5
Thanks @DaniFoldi! - fix: remove second Wrangler banner fromwrangler dispatch-namespace rename
2024-04-30
3.53.0
#5604
327a456
Thanks @dario-piotrowicz! - feat: add support for environments ingetPlatformProxy
allow
getPlatformProxy
to target environments by allowing users to specify anenvironment
optionExample usage:
const { env } = await getPlatformProxy({environment: "production",});#5705
4097759
Thanks @G4brym! - Addstaging
flag to AI binding
2024-04-24
3.52.0
#5666
81d9615
Thanks @CarmenPopoviciu! - fix: Fix Pages config validation around Durable ObjectsToday Pages cannot deploy Durable Objects itself. For this reason it is mandatory that when declaring Durable Objects bindings in the config file, the
script_name
is specified. We are currently not failing validation ifscript_name
is not specified but we should. These changes fix that.#5610
24840f6
Thanks @SuperchupuDev! - Markts-json-schema-generator
as a dev dependency#5669
a7e36d5
Thanks @dario-piotrowicz! - fix: fix broken Durable Object local proxying (when nocf
property is present)A regression was introduced in wrangler 3.46.0 ( https://github.com/cloudflare/workers-sdk/pull/5215) which made it so that missing
Request#cf
properties are serialized as"undefined"
, this in turn throws a syntax parse error when such values are parsed viaJSON.parse
breaking the communication with Durable Object local proxies. Fix such issue by serializing missingRequest#cf
properties as"{}"
instead.#5616
c6312b5
Thanks @webbertakken! - fix: broken link to durable object migrations docs#5482
1b7739e
Thanks @DaniFoldi! - docs: show new Discord url everywhere for consistency. The old URL still works, but https://discord.cloudflare.com is preferred.Updated dependencies [
3a0d735
,1b7739e
]:- [email protected]
- @cloudflare/[email protected]