chore(deps): update dependency wrangler to v3.58.0 #1626
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
3.53.1
->3.58.0
Release Notes
cloudflare/workers-sdk (wrangler)
v3.58.0
Compare Source
Minor Changes
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.Patch Changes
#5938
9e4d8bc
Thanks @threepointone! - fix: let "assets" in wrangler.toml be a stringThe 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 unknownUpdated dependencies [
e0e7725
]:v3.57.2
Compare Source
Patch Changes
#5905
53f22a0
Thanks @penalosa! - fix: Remove WARP certificate injection. Instead, you should ensure that any custom certificates that are needed are included inNODE_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 useExportedHandler["middleware"]
for injecting middlewareUpdated dependencies [
64ccdd6
,4458a9e
]:v3.57.1
Compare Source
Patch Changes
#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 unsuccessfulIf a Pages project fails to deploy,
wrangler pages deploy
will logan 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 devsv3.57.0
Compare Source
Minor Changes
#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:
This commit ensures that we provide users with:
#5814
2869e03
Thanks @CarmenPopoviciu! - fix: Display correct global flags inwrangler pages --help
Running
wrangler pages --help
will list, amongst others, the following global flags: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:
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 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.v3.56.0
Compare Source
Minor Changes
151bc3d
Thanks @penalosa! - feat: Supportmtls_certificates
andbrowser
bindings when usingwrangler.toml
with a Pages projectPatch Changes
#5813
9627cef
Thanks @GregBrimble! - fix: Upload Pages project assets with more graceUpdated dependencies [
0725f6f
,89b6d7f
]:v3.55.0
Compare Source
Minor Changes
#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.
Patch Changes
#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.
Updated dependencies [
66bdad0
,9b4af8a
]:Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.