Repository navigation
fix(ci): publish releases with patched Node 24 - #99
Merged
Merged
Conversation
github-actions Bot
pushed a commit
that referenced
this pull request
Oct 22, 2026
## [0.41.7](v0.41.6...v0.41.7) (2026-10-22) ### Bug Fixes * **ci:** publish releases with patched Node 24 ([#99](#99)) ([c823f88](c823f88))
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
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.
The security release builds all four SEA binaries, but its GitHub asset upload fails under Node 26.12.1 with
UND_ERR_INVALID_ARG: invalid content-length header. The current semantic-release GitHub plugin uses undici 7, which passes a numeric content-length to Node 26’s default dispatcher.Run only the semantic-release publishing job on patched Node 24.22.1. All shipped SEA binaries remain on patched Node 26.12.1.
Validation: a localhost upload using the actual installed undici 7.21.0 reproduces the failure under 26.12.1 and succeeds with HTTP 201 under 24.22.1; workflow YAML parses without errors; scoped Prettier and git diff checks pass. The failed v0.41.6 draft has no assets and was never published; this fix triggers a subsequent patch release without rewriting its tag.