ci(release): pin node to LTS to avoid undici break#2
Merged
Conversation
"latest" resolved to Node 26 on the runner, whose bundled undici rejects the onRequestStart interceptor that octokit/semantic-release registers, so every fetch failed in verifyConditions. Pin to lts/* (Node 24 line) which ships a compatible undici. Signed-off-by: Xe Iaso <xe@tigrisdata.com> Assisted-by: Claude Opus 4.8 via Claude Code Signed-off-by: Xe Iaso <xe@tigrisdata.com>
efirs
approved these changes
Jun 2, 2026
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.
Problem
The Cut Release workflow fails in
semantic-release'sverifyConditionsstep:Root cause
.github/workflows/release.yamlpinnedactions/setup-nodetonode-version: "latest", which resolved to Node.js 26 on the runner (confirmed by the error's user-agent:@semantic-release/github v12.0.8 octokit-core.js/7.0.6 Node.js/26).Node 26 bundles a newer undici whose request-dispatcher interceptor API changed and now rejects the
onRequestStartinterceptor that octokit/semantic-release registers. Every outboundfetch(e.g.GET /repos/tigrisdata/objgit) throws before reaching the GitHub API, killing the job.This is a Node/undici version incompatibility — not a token, permissions, or release-config problem.
Fix
Pin to
lts/*(currently the Node 24 line), which ships an undici compatible with the octokit stack.Verification
Re-run the Cut Release workflow via
workflow_dispatchand confirm the Setup Node step shows Node 24.x andsemantic-release --debuggets pastverifyConditionswithout theonRequestStarterror.