ci: bump release workflow to Node 22 for semantic-release v25 - #826
Merged
Merged
Conversation
semantic-release ^25 requires Node >=22.14 || >=24.10; the workflow pinned Node 20, so the Semantic Release job aborted before tagging and has failed the last three releases (no tag/changelog/GitHub release cut; deployed app unaffected). Latest tag stuck at v0.4.1.
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
1 participant
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.
Bump release workflow to Node 22
release.yamlpinsnode-version: "20", butsemantic-releaseis^25.0.3and v25 requires Node^22.14.0 || >= 24.10.0. The Semantic Release job therefore aborts immediately:Effect (pre-existing, not new)
The job has failed silently on the last three releases — #796 (2026-03-17), #799 (2026-03-20), and today's #825. No version tag, changelog entry, or GitHub Release is cut; the latest tag is stuck at
v0.4.1(2026-03-12). The deployed app is unaffected — Deploy to Azure runs inside the Build workflow, so production always carries the merged code. Only the versioning bookkeeping is broken.Change
One line:
node-version: "20"→"22"in.github/workflows/release.yaml. setup-node"22"resolves to the latest 22.x, satisfying the>= 22.14floor.Verification after merge
Once this reaches
main, the next Build→Release run should complete semantic-release cleanly and cut the first tag pastv0.4.1.Tracked in vault issue TEA — Release workflow Node version blocks semantic-release (epic: TEA — Performance & Tech-Debt).