From 44294f344b6061f176f809d9f63db32a3fc05d56 Mon Sep 17 00:00:00 2001 From: sonpiaz Date: Sat, 5 Sep 2026 14:31:17 -0700 Subject: [PATCH] chore(release): npm publish step no longer fails the release The token expires every 90 days; a red release for an expired secret hides nothing useful. Manual publish steps documented in docs/releases.md. Co-Authored-By: Claude Fable 5.1 Claude-Session: https://claude.ai/code/session_018Rok2mujdEZ2yGw8wVfbr9 --- .github/workflows/release.yml | 6 ++++++ docs/releases.md | 15 +++++++++++++++ 2 files changed, 21 insertions(+) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index 19f2334..76eced1 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -137,6 +137,12 @@ jobs: name: Publish @sonpiaz/watch-cli-mcp to npm needs: release runs-on: ubuntu-latest + # npm granular tokens expire every 90 days and the release must not hang + # on one. A red step here means "publish by hand": from mcp-server/, + # `npm version --no-git-tag-version `, `npm ci`, `npm run build`, + # `npm publish --access public` with a logged-in npm account (v0.3.4 was + # published that way on 2026-09-05). + continue-on-error: true steps: - name: Checkout uses: actions/checkout@v4 diff --git a/docs/releases.md b/docs/releases.md index 7a63c5a..c2e356a 100644 --- a/docs/releases.md +++ b/docs/releases.md @@ -24,6 +24,21 @@ contract: "v1 means the tarball at tag v1.x.y." --- +## When the npm step is red + +The `Publish @sonpiaz/watch-cli-mcp to npm` job is `continue-on-error`: npm +granular tokens expire every 90 days and a release should not fail because a +secret aged out. When it is red, publish by hand from a checkout of the tag: + +```bash +cd mcp-server +npm version --no-git-tag-version X.Y.Z +npm ci && npm run build +npm publish --access public +``` + +Then refresh `NPM_TOKEN` in the repository secrets when convenient. + ## Semver policy watch-cli follows semver with one pre-1.0 exception (see below).