Skip to content

Commit 2f73822

Browse files
committed
docs(releasing): the PAT is a workaround for an upstream bug, not how this works
The note from #73 explained the read:org cause and the working command, but read as though it described the registry's design. It does not: this is modelcontextprotocol/registry#1468, a maintainer confirmed it on 2026-07-27, and a fix is in progress. Written the old way, the next release reaches for a PAT it may no longer need and has no reason to check. So it now leads with "try the plain login first", attributes the cause upstream, and keeps the workaround as the fallback it is. Two details added because they cost time here and on that thread: the 403 blames private organisation membership, which belongs to an older code path and is not the gate — making a membership public is a visible change to a personal profile made for no reason. And the binary version is part of the picture: a user reports the workaround failing on 1.8.0 built 2026-07-13, while ours worked on 1.8.1 built 2026-08-06. Closes #90 Claude-Session: https://claude.ai/code/session_01SAFwE6SNvqnhhJ6p5X2W4F
1 parent dd680e0 commit 2f73822

1 file changed

Lines changed: 19 additions & 8 deletions

File tree

‎RELEASING.md‎

Lines changed: 19 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -117,14 +117,25 @@ mcp-publisher login github --token "$(gh auth token)" # see below — plain `l
117117
mcp-publisher publish # reads ./server.json from the cwd
118118
```
119119

120-
> **The org namespace needs a `read:org` token, and `mcp-publisher login github` does not mint one.**
121-
> The registry grants `io.github.<org>/*` only after calling `GET /user/memberships/orgs`, which
122-
> requires the `read:org` scope. A token without it gets a 403 that the registry **deliberately
123-
> swallows** as "no admin orgs" so personal publishing keeps working — so the device flow succeeds,
124-
> reports nothing wrong, and silently leaves you with `io.github.keparlak/*` only. The 403 from
125-
> `publish` then blames private org membership, which is about an older code path and is *not* the
126-
> gate. Passing a token that carries `read:org` (the `gh` CLI's does) is what actually works. This
127-
> cost three rounds of browser sign-in on the first submission.
120+
> **Try plain `mcp-publisher login github` first — the `--token` above is a workaround for a bug
121+
> that upstream is fixing.** If publishing still reports `You have permission to publish:
122+
> io.github.<your-username>/*`, the workaround is still needed.
123+
>
124+
> The cause, per [modelcontextprotocol/registry#1468][reg-1468]: since registry v1.8.0 only
125+
> organisation *Owners* may publish under an organisation namespace, and that is checked with
126+
> `GET /user/memberships/orgs`, which requires the `read:org` scope — a scope the GitHub App token
127+
> minted by `mcp-publisher login github` does not carry. The registry **deliberately swallows** the
128+
> resulting 403 as "no admin orgs" so personal publishing keeps working, so the device flow succeeds,
129+
> reports nothing wrong, and silently leaves you with your personal namespace. A maintainer confirmed
130+
> this on 2026-07-27 and a proper fix is in progress.
131+
>
132+
> Two traps worth knowing before you spend an afternoon on it, as v0.32.1 did. The 403 blames private
133+
> organisation membership; that belongs to an older code path and is **not** the gate — making a
134+
> membership public is a visible change to a personal profile made for no reason. And the binary
135+
> version matters: a user on that thread reports the workaround failing on `1.8.0` (built
136+
> 2026-07-13), while ours succeeded on `1.8.1` (built 2026-08-06).
137+
138+
[reg-1468]: https://github.com/modelcontextprotocol/registry/issues/1468
128139

129140
Two further conditions, both real: whoever publishes must be an **Owner** of `loncadev` (membership
130141
`role: admin`, `state: active` — an unaccepted invitation does not count), and the publish must come

0 commit comments

Comments
 (0)