chore: drop the npm self-upgrade from the publish workflow

Node 24 has bundled an npm new enough for trusted publishing since
24.4, so upgrading npm at publish time only added an unpinned install
to the release path. If a runner ever serves an older 24.x, npm publish
fails loudly rather than shipping anything.
This commit is contained in:
only-cli
2026-08-24 12:49:50 -04:00
parent bbe894bb96
commit 793e108a5c
+2 -3
View File
@@ -42,9 +42,8 @@ jobs:
- uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7.0.0
with:
node-version: 24
# Trusted publishing needs npm 11.5.1 or newer, pinned exactly so a
# release never runs an npm nobody reviewed.
- run: npm install -g npm@12.0.2
# Trusted publishing needs npm 11.5.1 or newer; node 24 has bundled a
# new-enough npm since 24.4, so nothing extra is installed here.
- run: npm ci
- run: npm test
- name: pick channel and version