Skip to content

Commit 55b347a

Browse files
bomly-guyclaude
andauthored
docs(ci): record the read:org gotcha for manual registry publishing (#360)
Publishing the first registry entry by hand failed twice with a 403 naming io.github.bomly-guy/* instead of io.github.bomly-dev/*. The interactive `mcp-publisher login github` flow does not request the read:org scope, so the registry cannot read the publisher's org role and falls back to the personal namespace. The 403 suggests making org membership public. That is a red herring — membership was made public and a freshly minted token still carried only the personal namespace. Passing a token that has read:org (the gh CLI's own token does) grants both namespaces immediately. io.github.bomly-dev/bomly-cli 0.21.1 is now live in the registry. Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
1 parent 4f36bac commit 55b347a

1 file changed

Lines changed: 13 additions & 0 deletions

File tree

dev-docs/CI.md

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -270,6 +270,19 @@ Two jobs at the end of `release.yml` publish the `bomly-mcp` npm wrapper and the
270270
gh variable set PUBLISH_MCP_REGISTRY -R bomly-dev/bomly-cli --body true
271271
```
272272

273+
### Publishing the registry entry by hand
274+
275+
Rarely needed — the release workflow does it — but useful for a first listing or a fix-up:
276+
277+
```bash
278+
mcp-publisher login github --token "$(gh auth token)"
279+
mcp-publisher publish
280+
```
281+
282+
**Use `--token`, not the bare interactive `mcp-publisher login github`.** The interactive OAuth flow does not request the `read:org` scope, so the registry cannot read your organization role and grants only your personal namespace (`io.github.<user>/*`). Publishing then fails with a 403 naming the wrong namespace. The error suggests making your org membership public; that alone does **not** fix it. A token carrying `read:org` does — and the `gh` CLI's own token already has it.
283+
284+
Publishing under `io.github.bomly-dev/*` also requires being an **Owner** of the org, which the registry checks.
285+
273286
### Notes
274287

275288
- **npm version floor.** Trusted publishing needs npm >= 11.5.1, which is newer than the runner image's bundled npm. The job installs `npm@^11.5.1` explicitly rather than inheriting whatever the image ships.

0 commit comments

Comments
 (0)