-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): update dependency wrangler to v3.22.4 #1331
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
ebbc5ce
to
d263cd1
Compare
d263cd1
to
31ab9c2
Compare
31ab9c2
to
7904c72
Compare
7904c72
to
e833d31
Compare
e833d31
to
abd7eb8
Compare
abd7eb8
to
b181da5
Compare
b181da5
to
a2bfa94
Compare
a2bfa94
to
bc6d987
Compare
bc6d987
to
88dc92d
Compare
88dc92d
to
5ff0ace
Compare
5ff0ace
to
fbcce19
Compare
fbcce19
to
d0ab31c
Compare
This PR contains the following updates:
3.14.0
->3.22.4
Release Notes
cloudflare/workers-sdk (wrangler)
v3.22.4
Compare Source
Patch Changes
#4699
4b4c1416
Thanks @mrbbot! - fix: prevent repeated reloads with circular service bindings[email protected]
introduced a bug where starting multiplewrangler dev
sessions with service bindings to each other resulted in a reload loop. This change ensures Wrangler only reloads when dependentwrangler dev
sessions start/stop.v3.22.3
Compare Source
Patch Changes
#4693
93e88c43
Thanks @mrbbot! - fix: ensurewrangler dev
exits with code0
on clean exitPreviously,
wrangler dev
would exit with a non-zero exit code when pressing CTRL+C or x. This change ensureswrangler
exits with code0
in these cases.#4630
037de5ec
Thanks @petebacondarwin! - fix: ensure User Worker gets the correct Host header in wrangler dev local modeSome full-stack frameworks, such as Next.js, check that the Host header for a server
side action request matches the host where the application is expected to run.
In
wrangler dev
we have a Proxy Worker in between the browser and the actual User Worker.This Proxy Worker is forwarding on the request from the browser, but then the actual User
Worker is running on a different host:port combination than that which the browser thinks
it should be on. This was causing the framework to think the request is malicious and blocking
it.
Now we update the request's Host header to that passed from the Proxy Worker in a custom
MF-Original-Url
header, but only do this if the request also contains a shared secret between the Proxy Worker
and User Worker, which is passed via the
MF-Proxy-Shared-Secret
header. This last feature is toprevent a malicious website from faking the Host header in a request directly to the User Worker.
Fixes https://github.com/cloudflare/next-on-pages/issues/588
0f8a03c0
Thanks @mrbbot! - fix: ensure API failures without additional messages logged correctly#4693
93e88c43
Thanks @mrbbot! - fix: ensurewrangler pages dev
exits cleanlyPreviously, pressing CTRL+C or x when running
wrangler pages dev
wouldn't actually exitwrangler
. You'd need to press CTRL+C a second time to exit the process. This change ensureswrangler
exits the first time.#4696
624084c4
Thanks @mrbbot! - fix: include additional modules inlargest dependencies
warningIf your Worker fails to deploy because it's too large, Wrangler will display of list of your Worker's largest dependencies. Previously, this just included JavaScript dependencies. This change ensures additional module dependencies (e.g. WebAssembly, text blobs, etc.) are included when computing this list.
Updated dependencies [
037de5ec
]:v3.22.2
Compare Source
Patch Changes
#4600
4233e514
Thanks @mrbbot! - fix: apply source mapping to deployment validation errorsPreviously if a Worker failed validation during
wrangler deploy
, the displayed error would reference locations in built JavaScript files. This made it more difficult to debug validation errors. This change ensures these errors are now source mapped, referencing locations in source files instead.#4440
15717333
Thanks @mrbbot! - fix: automatically create required directories forwrangler r2 object get
Previously, if you tried to use
wrangler r2 object get
with an object name containing a/
or used the--file
flag with a path containing a/
, and the specified directory didn't exist, Wrangler would throw anENOENT
error. This change ensures Wrangler automatically creates required parent directories if they don't exist.#4592
20da658e
Thanks @mrbbot! - fix: throw helpful error if email validation requiredPreviously, Wrangler would display the raw API error message and code if email validation was required during
wrangler deploy
. This change ensures a helpful error message is displayed instead, prompting users to check their emails or visit the dashboard for a verification link.e1d50407
Thanks @mrbbot! - fix: suggest checking permissions on authentication error with API token setc370026d
Thanks @mrbbot! - fix: include messages from API in errors#4588
4e5ed0b2
Thanks @mrbbot! - fix: require worker name for rollbackPreviously, Wrangler would fail with a cryptic error if you tried to run
wrangler rollback
outside of a directory containing a Wrangler configuration file with aname
defined. This change validates that a worker name is defined, and allows you to set it from the command line using the--name
flag.Updated dependencies [
c410ea14
]:v3.22.1
Compare Source
Patch Changes
#4635
5bc2699d
Thanks @mrbbot! - fix: prevent zombieworkerd
processesPreviously, running
wrangler dev
would leave behind "zombie"workerd
processes. These processes prevented the same port being bound ifwrangler dev
was restarted and sometimes consumed lots of CPU time. This change ensures allworkerd
processes are killed whenwrangler dev
is shutdown.To clean-up existing zombie processes, run
pkill -KILL workerd
on macOS/Linux ortaskkill /f /im workerd.exe
on Windows.v3.22.0
Compare Source
Minor Changes
a6a4e8a4
Thanks @G4brym! - Deprecate constellation commands and add a warning when using the constellation bindinge8a2a1d9
Thanks @vkrasnov! - Added support for R2 Sippy incremental migration98dee932
Thanks @rozenmd! - feat: add rows written/read in the last 24 hours towrangler d1 info
outputc628de59
Thanks @OilyLime! - Improve queues list displaying as table, update queues API typesv3.21.0
Compare Source
Minor Changes
#4423
a94ef570
Thanks @mrbbot! - feat: apply source mapping to logged stringsPreviously, Wrangler would only apply source mapping to uncaught exceptions. This meant if you caught an exception and logged its stack trace, the call sites would reference built JavaScript files as opposed to source files. This change looks for stack traces in logged messages, and tries to source map them.
Note source mapping is only applied when outputting logs.
Error#stack
does not return a source mapped stack trace. This means the actual runtime value ofnew Error().stack
and the output fromconsole.log(new Error().stack)
may be different.Patch Changes
66394681
Thanks @huw! - Add 'took recursive isolate lock' warning to workerd output exceptionsv3.20.0
Compare Source
Minor Changes
c10bf0fd
Thanks @G4brym! - Add support for Workers AI in local mode#4571
3314dbde
Thanks @penalosa! - feat: When Wrangler crashes, send an error report to Sentry to aid in debugging.When Wrangler's top-level exception handler catches an error thrown from Wrangler's application, it will offer to report the error to Sentry. This requires opt-in from the user every time.
Patch Changes
4c85fe99
Thanks @dario-piotrowicz! - During the R2 validation, showMAX_UPLOAD_SIZE
errors using MiB (consistently with the Cloudflare docs)#4577
4c85fe99
Thanks @dario-piotrowicz! - During the Pages validation, showMAX_UPLOAD_SIZE
errors using MiB (consistently with the Cloudflare docs)Updated dependencies [
eb08e2dc
]:v3.19.0
Compare Source
Minor Changes
#4547
86c81ff0
Thanks @mrbbot! - fix: listen on IPv4 loopback only by default on WindowsDue to a known issue,
workerd
will only listen on the IPv4 loopback address127.0.0.1
when it's asked to listen onlocalhost
. On Node.js > 17,localhost
will resolve to the IPv6 loopback address, meaning requests toworkerd
would fail. This change switches to using the IPv4 loopback address throughout Wrangler on Windows, while workerd#1408 gets fixed.#4535
29df8e17
Thanks @mrbbot! - Reintroduces some internal refactorings of wrangler dev servers (includingwrangler dev
,wrangler dev --remote
, andunstable_dev()
).These changes were released in 3.13.0 and reverted in 3.13.1 -- we believe the changes are now more stable and ready for release again.
There are no changes required for developers to opt-in. Improvements include:
Patch Changes
6c5bc704
Thanks @zebp! - fix: init from dash specifying explicit usage model in wrangler.toml for standard users#4550
63708a94
Thanks @mrbbot! - fix: validateHost
andOrgin
headers where appropriateHost
andOrigin
headers are now checked when connecting to the inspector and Miniflare's magic proxy. If these don't match what's expected, the request will fail.Updated dependencies [
71fb0b86
,63708a94
]:v3.18.0
Compare Source
Minor Changes
#4532
311ffbd5
Thanks @mrbbot! - fix: changewrangler (pages) dev
to listen onlocalhost
by defaultPreviously, Wrangler listened on all interfaces (
*
) by default. This change switcheswrangler (pages) dev
to just listen on local interfaces. Whilst this is technically a breaking change, we've decided the security benefits outweigh the potential disruption caused. If you need to access your dev server from another device on your network, you can usewrangler (pages) dev --ip *
to restore the previous behaviour.Patch Changes
1b348782
]:v3.17.1
Compare Source
Patch Changes
#4474
382ef8f5
Thanks @mrbbot! - fix: open browser to correct url pressingb
in--remote
modeThis change ensures Wrangler doesn't try to open
http://*
when*
is used as the dev server's hostname. Instead, Wrangler will now openhttp://127.0.0.1
.#4488
3bd57238
Thanks @RamIdeas! - Changes the default directory for log files to workaround frameworks that are watching the entire.wrangler
directory in the project root for changesAlso includes a fix for commands with
--json
where the log file location message would cause stdout to not be valid JSON. That message now goes to stderr.v3.17.0
Compare Source
Minor Changes
#4341
d9908743
Thanks @RamIdeas! - Wrangler now writes all logs to a .log file in the.wrangler
directory. Set a directory or specific .log filepath to write logs to withWRANGLER_LOG_PATH=../Desktop/my-logs/
orWRANGLER_LOG_PATH=../Desktop/my-logs/my-log-file.log
. When specifying a directory or using the default location, a filename with a timestamp is used.Wrangler now filters workerd stdout/stderr and marks unactionable messages as debug logs. These debug logs are still observable in the debug log file but will no longer show in the terminal by default without the user setting the env var
WRANGLER_LOG=debug
.Patch Changes
d5e1966b
Thanks @mrbbot! - fix: report correct line and column numbers when source mapping errors withwrangler dev --remote
1747d215
Thanks @rozenmd! - fix: make it possible to ignore hyperdrive warnings805d5241
Thanks @dario-piotrowicz! - add warnings about ai and verctorize bindings not being supported locally#4478
7b54350b
Thanks @penalosa! - Don't log sensitive data to the Wrangler debug log file by default. This includes API request headers and responses.Updated dependencies [
be2b9cf5
,d9908743
]:v3.16.0
Compare Source
Minor Changes
102e15f9
Thanks @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
dd270d00
Thanks @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
baa76e77
Thanks @rozenmd! - This PR adds a fetch handler that usespage
, assumingresult_info
provided by the endpoint containspage
,per_page
, andtotal
This is needed as the existing
fetchListResult
handler for fetching potentially paginated results doesn't work for endpoints that don't implementcursor
.Fixes #4349
#4337
6c8f41f8
Thanks @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.7fbe1937
Thanks @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 interfacesf867e01c
Thanks @tmthecoder! - Support for hyperdrive bindings in local wrangler dev7e05f38e
Thanks @jspspike! - Fixed issue withtail
not using proxy0453b447
Thanks @maxwellpeterson! - Allows uploads with both cron triggers and smart placement enabled#4437
05b1bbd2
Thanks @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
]:v3.15.0
Compare Source
Minor Changes
0cac2c46
Thanks @penalosa! - Callout--minify
when script size is too large#4209
24d1c5cf
Thanks @mrbbot! - fix: suppress compatibility date fallback warnings if nowrangler
update is availableIf a compatibility date greater than the installed version of
workerd
wasconfigured, a warning would be logged. This warning was only actionable if a new
version of
wrangler
was available. The intent here was to warn if a user seta new compatibility date, but forgot to update
wrangler
meaning changesenabled by the new date wouldn't take effect. This change hides the warning if
no update is available.
It also changes the default compatibility date for
wrangler dev
sessionswithout a configured compatibility date to the installed version of
workerd
.This previously defaulted to the current date, which may have been unsupported
by the installed runtime.
#4135
53218261
Thanks @Cherry! - feat: resolve npm exports for file importsPreviously, when using wasm (or other static files) from an npm package, you would have to import the file like so:
This update now allows you to import the file like so, assuming it's exposed and available in the package's
exports
field:This will look at the package's
exports
field inpackage.json
and resolve the file usingresolve.exports
.#4232
69b43030
Thanks @romeupalos! - fix: usezone_name
to determine a zone when the pattern is a custom hostnameIn Cloudflare for SaaS, custom hostnames of third party domain owners can be used in Cloudflare.
Workers are allowed to intercept these requests based on the routes configuration.
Before this change, the same logic used by
wrangler dev
was used inwrangler deploy
, which caused wrangler to fail with:✘ [ERROR] Could not find zone for [partner-saas-domain.com]
b404ab70
Thanks @penalosa! - When uploading additional modules with your worker, Wrangler will now report the (uncompressed) size of each individual module, as well as the aggregate size of your WorkerPatch Changes
950bc401
Thanks @RamIdeas! - fix various logging of shell commands to correctly quote args when needed#4274
be0c6283
Thanks @jspspike! - chore: bumpminiflare
to3.20231025.0
This change enables Node-like
console.log()
ing in local mode. Objects withlots of properties, and instances of internal classes like
Request
,Headers
,ReadableStream
, etc will now be logged with much more detail.#4127
3d55f965
Thanks @mrbbot! - fix: store temporary files in.wrangler
As Wrangler builds your code, it writes intermediate files to a temporary
directory that gets cleaned up on exit. Previously, Wrangler used the OS's
default temporary directory. On Windows, this is usually on the
C:
drive.If your source code was on a different drive, our bundling tool would generate
invalid source maps, breaking breakpoint debugging. This change ensures
intermediate files are always written to the same drive as sources. It also
ensures unused build outputs are cleaned up when running
wrangler pages dev
.This change also means you no longer need to set
cwd
andresolveSourceMapLocations
in.vscode/launch.json
when creating anattach
configuration for breakpoint debugging. Your
.vscode/launch.json
should nowlook something like...
05798038
Thanks @gabivlj! - Move helper cli files of C3 into @cloudflare/cli and make Wrangler and C3 depend on it#4235
46cd2df5
Thanks @mrbbot! - fix: ensureconsole.log()
s during startup are displayedPreviously,
console.log()
calls before the Workers runtime was ready toreceive requests wouldn't be shown. This meant any logs in the global scope
likely weren't visible. This change ensures startup logs are shown. In particular,
this should fix Remix's HMR,
which relies on startup logs to know when the Worker is ready.
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.