-
Notifications
You must be signed in to change notification settings - Fork 747
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
Version Packages #4691
Version Packages #4691
Conversation
A wrangler prerelease is available for testing. You can install this latest build in your project with: npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/7412431000/npm-package-wrangler-4691 You can reference the automatically updated head of this PR with: npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/prs/7412431000/npm-package-wrangler-4691 Or you can use npx https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/7412431000/npm-package-wrangler-4691 dev path/to/script.js Additional artifacts:npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/7412431000/npm-package-miniflare-4691 npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/7412431000/npm-package-cloudflare-pages-shared-4691 npx https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/7412431000/npm-package-create-cloudflare-4691 --no-auto-update Note that these links will no longer work once the GitHub Actions artifact expires.
| Please ensure constraints are pinned, and |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #4691 +/- ##
==========================================
+ Coverage 75.58% 75.64% +0.05%
==========================================
Files 243 243
Lines 13096 13096
Branches 3375 3375
==========================================
+ Hits 9899 9906 +7
+ Misses 3197 3190 -7 |
e2b0c21
to
95a1cf6
Compare
433d91d
to
8d99a34
Compare
8d99a34
to
009d8cd
Compare
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
create-cloudflare@2.9.0
Minor Changes
e8053554
Thanks @dario-piotrowicz! - Create a custom not-found edge route for Next.js applications using the app routerPatch Changes
9e032723
Thanks @dependabot! - C3: Bumpedgatsby
from5.12.12
to5.13.1
miniflare@3.20231218.1
Patch Changes
#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 [🐛 Bug]: Server actions don't work with
wrangler pages dev
next-on-pages#588@cloudflare/pages-shared@0.11.6
Patch Changes
037de5ec
]:wrangler@3.22.3
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 [🐛 Bug]: Server actions don't work with
wrangler pages dev
next-on-pages#588#4695
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
]: