From ef0a5cc880ca8e467c09ae22770b1e93bd3c9297 Mon Sep 17 00:00:00 2001 From: Freeman Date: Fri, 1 May 2026 10:27:52 +0100 Subject: [PATCH 1/2] ci: drop npm self-upgrade step that breaks on node 22 runner The "Upgrade npm for OIDC support" step fails with MODULE_NOT_FOUND on promise-retry when the bundled npm 22.x on ubuntu-latest tries to install npm@latest. The step was historically added to get a new-enough npm for --provenance, but actions/setup-node@v4 with Node 22 already ships a provenance-capable npm. Remove the step. --- .github/workflows/release.yml | 3 --- 1 file changed, 3 deletions(-) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index ec52510..efe6c36 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -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]" From 49e93dd81b7d27049a8a825d45f58194cdb017ef Mon Sep 17 00:00:00 2001 From: Freeman Date: Fri, 1 May 2026 10:28:03 +0100 Subject: [PATCH 2/2] docs: add PR write-up for Fix release workflow by removing broken npm self-upgrade step --- .../2026-05-01-fix-release-npm-upgrade.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 documentation/PULL_REQUESTS/2026-05-01-fix-release-npm-upgrade.md diff --git a/documentation/PULL_REQUESTS/2026-05-01-fix-release-npm-upgrade.md b/documentation/PULL_REQUESTS/2026-05-01-fix-release-npm-upgrade.md new file mode 100644 index 0000000..895dd65 --- /dev/null +++ b/documentation/PULL_REQUESTS/2026-05-01-fix-release-npm-upgrade.md @@ -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)