chore(deps): update dependency wrangler to v3.99.0 #7286
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.95.0
->3.99.0
Release Notes
cloudflare/workers-sdk (wrangler)
v3.99.0
Compare Source
Minor Changes
#7425
8757579
Thanks @CarmenPopoviciu! - feat: Make DX improvements inwrangler dev --remote
Workers + Assets projects have, in certain situations, a relatively degraded
wrangler dev --remote
developer experience, as opposed to Workers proper projects. This is due to the fact that, for Workers + Assets, we need to make extra API calls to:This commit improves the
wrangler dev --remote
DX for Workers + Assets, for use cases when the User Worker/assets change while the API calls for previous changes are still in flight. For such use cases, we have put an exit early strategy in place, that drops the event handler execution of the previous changes, in favour of the handler triggered by the new changes.#7537
086a6b8
Thanks @WillTaylorDev! - Provide validation around assets.experimental_serve_directly#7568
2bbcb93
Thanks @WillTaylorDev! - Warn users when using smart placement with Workers + Assets andserve_directly
is set tofalse
Patch Changes
#7521
48e7e10
Thanks @emily-shen! - feat: add experimental_patchConfig()experimental_patchConfig()
can add to a user's config file. It preserves comments if its awrangler.jsonc
. However, it is not suitable forwrangler.toml
with comments as we cannot preserve comments on write.Updated dependencies [
1488e11
,7216835
]:v3.98.0
Compare Source
Minor Changes
#7476
5124b5d
Thanks @WalshyDev! - feat: allow routing to Workers with Assets on any HTTP route, not just the root. For example,example.com/blog/*
can now be used to serve assets.These assets will be served as though the assets directly were mounted to the root.
For example, if you have
assets = { directory = "./public/" }
, a route like"example.com/blog/*"
and a file./public/blog/logo.png
, this will be available atexample.com/blog/logo.png
. Assets outside of directories which match the configured HTTP routes can still be accessed with the Assets binding or with a Service binding to this Worker.#7380
72935f9
Thanks @CarmenPopoviciu! - Add Workers + Assets support inwrangler dev --remote
Patch Changes
#7573
fb819f9
Thanks @emily-shen! - feat: add experimental_readRawConfig()Adds a Wrangler API to find and read a config file
#7549
42b9429
Thanks @penalosa! - Expand metrics collection to:--x-versions
,--x-dev-env
, and--latest
) by only including args that were inargv
#7583
8def8c9
Thanks @penalosa! - Revert support for custom unenv resolve path to address an issue with Wrangler failing to deploy Pages projects withnodejs_compat_v2
in some casesv3.97.0
Compare Source
Minor Changes
#7522
6403e41
Thanks @vicb! - feat(wrangler): allow overriding the unenv preset.By default wrangler uses the bundled unenv preset.
Setting
WRANGLER_UNENV_RESOLVE_PATHS
allow to use another version of the preset.Those paths are used when resolving the unenv module identifiers to absolute paths.
This can be used to test a development version.
#7479
2780849
Thanks @penalosa! - Accept a JSON file of the format{ name: string }[]
inwrangler kv bulk delete
, as well as the currentstring[]
format.Patch Changes
#7541
ca9410a
Thanks @vicb! - chore(wrangler): update unenv dependency version#7345
15aa936
Thanks @edmundhung! - fix(wrangler): keypress event name is optionalv3.96.0
Compare Source
Minor Changes
#7510
004af53
Thanks @oliy! - Add file prefix option to wrangler pipelines commands#7383
8af3365
Thanks @jonesphillip! - Added wrangler r2 domain get commandPatch Changes
#7542
f13c897
Thanks @CarmenPopoviciu! - Always print deployment and placement ID in Cloudchamber commandsCurrently, Cloudchamber commands only print the full deployment ID when the deployment has an IPv4 address. This commit ensures the deployment ID and the placement ID are always printed to stdout. It also moves the printing of the IPv4 address (if one exists) to the same place as the IPv6 address so that they are printed together.
#6754
0356d0a
Thanks @bluwy! - refactor: move@cloudflare/workers-shared
as dev dependency#7478
2e90efc
Thanks @petebacondarwin! - fix: ensure that non-inherited fields are not removed when using an inferred named environmentIt is an error for the the user to provide an environment name that doesn't match any of the named environments in the Wrangler configuration.
But if there are no named environments defined at all in the Wrangler configuration, we special case the top-level environment as though it was a named environment.
Previously, when this happens, we would remove all the nonInheritable fields from the configuration (essentially all the bindings) leaving an incorrect configuration.
Now we correctly generate a flattened named environment that has the nonInheritable fields, plus correctly applies any transformFn on inheritable fields.
#7524
11f95f7
Thanks @gpanders! - Include response body in Cloudchamber API errors#7427
3bc0f28
Thanks @edmundhung! - Thex-provision
experimental flag now identifies draft and inherit bindings by looking up the current binding settings.Draft bindings can then be provisioned (connected to new or existing KV, D1, or R2 resources) during
wrangler deploy
.Updated dependencies []:
Configuration
📅 Schedule: Branch creation - "before 8am every weekday,every weekend" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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 was generated by Mend Renovate. View the repository job log.