Conversation
Node >=24.14 ships an undici version with a regression that breaks publish-browser-extension's Edge upload with "expected non-null body source" when fetch() is given a Request with a body and the server returns a non-2xx. The Edge step in v1.2.0 publish failed because of this. Test workflow stays on the 20/22/24 matrix; only the publish job needs the pin since it's the only one exercising fetch-with-Request-body against external store APIs. Ref: vercel/next.js#90826 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #14 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 1 1
Lines 4 4
Branches 1 1
=========================================
Hits 4 4 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
v1.2.0 Edge publish failed with `expected non-null body source` — a Node >=24.14 undici regression hit by publish-browser-extension's Edge upload. Pinning the publish workflow to Node 22. Chrome and Firefox already shipped successfully and will be skipped on re-run via their store-version gates; only Edge will actually publish.
Ref: vercel/next.js#90826