Skip to content

Fix release workflow by removing broken npm self-upgrade step #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
nabilfreeman merged 2 commits into from
May 1, 2026
Merged

Fix release workflow by removing broken npm self-upgrade step #2

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ef0a5cc
ci: drop npm self-upgrade step that breaks on node 22 runner
nabilfreeman May 1, 2026
49e93dd
docs: add PR write-up for Fix release workflow by removing broken npm…
nabilfreeman May 1, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 0 additions & 3 deletions .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,9 +47,6 @@ jobs:

# ── Mutating steps (only reached if tests pass) ───────────────────

- name: Upgrade npm for OIDC support
run: npm install -g npm@latest

- name: Configure Git
run: |
git config user.name "github-actions[bot]"
Expand Down
16 changes: 16 additions & 0 deletions documentation/PULL_REQUESTS/2026-05-01-fix-release-npm-upgrade.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
## Problem

Our release workflow failed on the very first run after introducing CI — not on any of our changes, but on an infrastructure step that was already there: an attempt to upgrade npm that no longer works on the current GitHub Actions runner. Tests passed, so nothing broken was shipped, but the version bump and publish never happened.

## Solution

Remove the broken step. The npm version that ships with the Node 22 runner already supports the features we need, so upgrading it is unnecessary — and currently impossible due to an upstream bug in npm's self-upgrade path.

## Impact

Once this merges, re-running the release workflow should publish a new version cleanly.

# Credits

- Nabs (Architect)
- JENA (Lead Developer)
Loading