webgrip/semantic-release-config
5
0
Fork 0
Code Issues Pull requests 1 Projects Releases 5 Packages 1 Wiki Activity Actions

ci: run release/test on Node 22 — semantic-release refuses Node 20 #5

Open
ryangr0 wants to merge 1 commit from ryangr0/ci/node-22-release into main AGit
pull from: ryangr0/ci/node-22-release
merge into: webgrip:main
Conversation 0 Commits 1 Files changed 2 +3 -3
ryangr0 commented 2026-07-26 20:58:05 +00:00
Owner
Copy link

Release runs 15/17/19 died at semantic-release's engine check (needs ^22.14.0 || >=24.10.0, runner had 20.20.2), so v1.0.2 is the last published version and the parser fix, helm bump and verify-gate cache write are all stuck on main unreleased. Node 22 not 24: satisfies the engine range while keeping npm 10 — npm 11 has the %2F-decode regression that 404s scoped packages on Forgejo (this repo publishes one; the infrastructure composite already pins npm for the same reason). Merging re-runs release.yml on the merge push and the backlog cuts as one minor (v1.1.0). Generated with Claude Code.

Release runs 15/17/19 died at semantic-release's engine check (needs ^22.14.0 || >=24.10.0, runner had 20.20.2), so v1.0.2 is the last published version and the parser fix, helm bump and verify-gate cache write are all stuck on main unreleased. Node 22 not 24: satisfies the engine range while keeping npm 10 — npm 11 has the %2F-decode regression that 404s scoped packages on Forgejo (this repo publishes one; the infrastructure composite already pins npm for the same reason). Merging re-runs release.yml on the merge push and the backlog cuts as one minor (v1.1.0). Generated with Claude Code.
ci: run release/test on Node 22 — semantic-release refuses Node 20
All checks were successful
Test / test (pull_request) Successful in 1m39s
Details
9e731ca487 
Release runs 15/17/19 all died in one second at the engine check: the lockfile's
semantic-release now requires ^22.14.0 || >=24.10.0 and setup-node pinned "20"
(found v20.20.2). Nothing has published since v1.0.2 — the parser fix, the helm
bump and the verify-gate cache write all sit unreleased on main.

Node 22, deliberately not 24: 22.x satisfies the engine range while still
bundling npm 10.x. Node 24's npm 11 intermittently decodes the scope's %2F in
scoped-package URLs, which Forgejo's npm routes 404 — that regression is why the
infrastructure composite pins npm@11.4.2 — and THIS repo npm-publishes a scoped
package with the same client, so it stays on npm 10 until Forgejo tolerates the
decoded form.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
All checks were successful
Test / test (pull_request) Successful in 1m39s
Details
This pull request has changes conflicting with the target branch.
  • .forgejo/workflows/release.yml
  • .forgejo/workflows/test.yml
View command line instructions

Manual merge helper

Use this merge commit message when completing the merge manually.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin +refs/pull/5/head:ryangr0/ci/node-22-release
git switch ryangr0/ci/node-22-release

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main
git merge --no-ff ryangr0/ci/node-22-release
git switch ryangr0/ci/node-22-release
git rebase main
git switch main
git merge --ff-only ryangr0/ci/node-22-release
git switch ryangr0/ci/node-22-release
git rebase main
git switch main
git merge --no-ff ryangr0/ci/node-22-release
git switch main
git merge --squash ryangr0/ci/node-22-release
git switch main
git merge --ff-only ryangr0/ci/node-22-release
git switch main
git merge ryangr0/ci/node-22-release
git push origin main
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
webgrip/semantic-release-config!5
No description provided.