Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
6 changes: 6 additions & 0 deletions .github/workflows/release.yml
Original file line number Diff line number Diff line change
Expand Up @@ -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 <tag>`, `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
Expand Down
15 changes: 15 additions & 0 deletions docs/releases.md
Original file line number Diff line number Diff line change
Expand Up @@ -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).
Expand Down
Loading