Bump wrangler from 3.5.1 to 3.16.0
Bumps wrangler from 3.5.1 to 3.16.0.
Release notes
Sourced from wrangler's releases.
[email protected]
Minor Changes
- #4347
102e15f9Thanks@Skye-31! - Feat(unstable_dev): Provide an option for unstable_dev to perform the check that prompts users to update wrangler, defaulting to false. This will prevent unstable_dev from sending a request to NPM on startup to determine whether it needs to be updated.
#4179
dd270d00Thanks@matthewdavidrodgers! - Simplify secret:bulk api via script settingsFiring PUTs to the secret api in parallel has never been a great solution - each request independently needs to lock the script, so running in parallel is at best just as bad as running serially.
Luckily, we have the script settings PATCH api now, which can update the settings for a script (including secret bindings) at once, which means we don't need any parallelization. However this api doesn't work with a partial list of bindings, so we have to fetch the current bindings and merge in with the new secrets before PATCHing. We can however just omit the value of the binding (i.e. only provide the name and type) which instructs the config service to inherit the existing value, which simplifies this as well. Note that we don't use the bindings in your current wrangler.toml, as you could be in a draft state, and it makes sense as a user that a bulk secrets update won't update anything else. Instead, we use script settings api again to fetch the current state of your bindings.
This simplified implementation means the operation can only fail or succeed, rather than succeeding in updating some secrets but failing for others. In order to not introduce breaking changes for logging output, the language around "${x} secrets were updated" or "${x} secrets failed" is kept, even if it doesn't make much sense anymore.
Patch Changes
#4402
baa76e77Thanks@rozenmd! - This PR adds a fetch handler that usespage, assumingresult_infoprovided by the endpoint containspage,per_page, andtotalThis is needed as the existing
fetchListResulthandler for fetching potentially paginated results doesn't work for endpoints that don't implementcursor.Fixes #4349
#4337
6c8f41f8Thanks@Skye-31! - Improve the error message when a script isn't exported a Durable Object classPreviously, wrangler would error with a message like
Uncaught TypeError: Class extends value undefined is not a constructor or null. This improves that messaging to be more understandable to users.
- #4307
7fbe1937Thanks@jspspike! - Change local dev server default ip to*instead of0.0.0.0. This will cause the dev server to listen on both ipv4 and ipv6 interfaces
- #4222
f867e01cThanks@tmthecoder! - Support for hyperdrive bindings in local wrangler dev
- #4149
7e05f38eThanks@jspspike! - Fixed issue withtailnot using proxy
- #4219
0453b447Thanks@maxwellpeterson! - Allows uploads with both cron triggers and smart placement enabled
#4437
05b1bbd2Thanks@jspspike! - Change dev registry and inspector server to listen on 127.0.0.1 instead of all interfacesUpdated dependencies [
4f8b3420,16cc2e92,3637d97a,29a59d4e,7fbe1937,76787861,8a25b7fb]:[email protected]
Minor Changes
#4201
0cac2c46Thanks@penalosa! - Callout--minifywhen script size is too large#4209
24d1c5cfThanks@mrbbot! - fix: suppress compatibility date fallback warnings if nowranglerupdate is availableIf a compatibility date greater than the installed version of
workerdwas configured, a warning would be logged. This warning was only actionable if a new version ofwranglerwas available. The intent here was to warn if a user set a new compatibility date, but forgot to updatewranglermeaning changes
... (truncated)
Changelog
Sourced from wrangler's changelog.
3.16.0
Minor Changes
- #4347
102e15f9Thanks@Skye-31! - Feat(unstable_dev): Provide an option for unstable_dev to perform the check that prompts users to update wrangler, defaulting to false. This will prevent unstable_dev from sending a request to NPM on startup to determine whether it needs to be updated.
#4179
dd270d00Thanks@matthewdavidrodgers! - Simplify secret:bulk api via script settingsFiring PUTs to the secret api in parallel has never been a great solution - each request independently needs to lock the script, so running in parallel is at best just as bad as running serially.
Luckily, we have the script settings PATCH api now, which can update the settings for a script (including secret bindings) at once, which means we don't need any parallelization. However this api doesn't work with a partial list of bindings, so we have to fetch the current bindings and merge in with the new secrets before PATCHing. We can however just omit the value of the binding (i.e. only provide the name and type) which instructs the config service to inherit the existing value, which simplifies this as well. Note that we don't use the bindings in your current wrangler.toml, as you could be in a draft state, and it makes sense as a user that a bulk secrets update won't update anything else. Instead, we use script settings api again to fetch the current state of your bindings.
This simplified implementation means the operation can only fail or succeed, rather than succeeding in updating some secrets but failing for others. In order to not introduce breaking changes for logging output, the language around "${x} secrets were updated" or "${x} secrets failed" is kept, even if it doesn't make much sense anymore.
Patch Changes
#4402
baa76e77Thanks@rozenmd! - This PR adds a fetch handler that usespage, assumingresult_infoprovided by the endpoint containspage,per_page, andtotalThis is needed as the existing
fetchListResulthandler for fetching potentially paginated results doesn't work for endpoints that don't implementcursor.Fixes #4349
#4337
6c8f41f8Thanks@Skye-31! - Improve the error message when a script isn't exported a Durable Object classPreviously, wrangler would error with a message like
Uncaught TypeError: Class extends value undefined is not a constructor or null. This improves that messaging to be more understandable to users.
- #4307
7fbe1937Thanks@jspspike! - Change local dev server default ip to*instead of0.0.0.0. This will cause the dev server to listen on both ipv4 and ipv6 interfaces
- #4222
f867e01cThanks@tmthecoder! - Support for hyperdrive bindings in local wrangler dev
- #4149
7e05f38eThanks@jspspike! - Fixed issue withtailnot using proxy
- #4219
0453b447Thanks@maxwellpeterson! - Allows uploads with both cron triggers and smart placement enabled
#4437
05b1bbd2Thanks@jspspike! - Change dev registry and inspector server to listen on 127.0.0.1 instead of all interfacesUpdated dependencies [
4f8b3420,16cc2e92,3637d97a,29a59d4e,7fbe1937,76787861,8a25b7fb]:3.15.0
Minor Changes
- #4201
0cac2c46Thanks@penalosa! - Callout--minifywhen script size is too large
#4209
24d1c5cfThanks@mrbbot! - fix: suppress compatibility date fallback warnings if nowranglerupdate is availableIf a compatibility date greater than the installed version of
workerdwas configured, a warning would be logged. This warning was only actionable if a new version ofwranglerwas available. The intent here was to warn if a user set
... (truncated)
Commits
08615aaVersion Packages (#4291)2be0f3fPack miniflare for e2e (#4458)05b1bbdChange dev registry and inspector server to use 127.0.0.1 instead of all inte...3753eafRevert "feat(workers): allow namespaced scripts to be used as Worker tail con...f212fbdRevert "tail: add a --yes flag to bypass the DO prompt (#4350)" (#4446)baa76e7fix(fetch): use pages for pagination instead of cursor (#4402)7fbe193Change default ip for dev server from0.0.0.0to*(#4307)9bc52cfImprove Testing (#4325)6c8f41fFix: provide proper error message for missing DOs (#4337)f867e01wrangler: Hyperdrive dev bindings (#4222)- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
-
@dependabot rebasewill rebase this PR -
@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it -
@dependabot mergewill merge this PR after your CI passes on it -
@dependabot squash and mergewill squash and merge this PR after your CI passes on it -
@dependabot cancel mergewill cancel a previously requested merge and block automerging -
@dependabot reopenwill reopen this PR if it is closed -
@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency -
@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)