Skip to content

ci: wait for npm before the MCP Registry; add a registry-only workflow - #10

Merged
tiltom merged 1 commit into
mainfrom
ci/mcp-registry-retry
Nov 10, 2026
Merged

tiltom merged 1 commit into
mainfrom
ci/mcp-registry-retry

Conversation

@tiltom

@tiltom tiltom commented Nov 10, 2026 •

Copy link
Copy Markdown
Member

Why

The v0.5.1 Release run (42884948030) published flagrix@0.5.1 to npm. About a second later it sent server.json to the MCP Registry, which checks npm. npm didn't serve 0.5.1 yet, so the registry rejected it with a 400 ("version '0.5.1' was not found"). The registry still lists 0.5.0 as latest.

This can't be fixed by re-running the run, because its npm publish would fail on the version that now exists. Publishing from a laptop doesn't work either. mcp-publisher login github only grants io.github.tiltom/*, and the io.github.flagrix-io namespace needs GitHub Actions OIDC or a classic PAT with read:org.

What changed

  • scripts/wait-for-npm.sh <package> <version> [timeout] waits until npm serves the version, checking both /flagrix/<version> and the package's version list. It checks every 20 s for up to 15 min.
  • release.yml runs it between npm publish and the registry steps.
  • New mcp-registry.yml (manual, input tag) publishes the tag's server.json to the registry over OIDC without touching npm. It checks that both versions in server.json match the tag and waits for npm before publishing. It checks out the branch it is run from and reads server.json from the tag, so it also works for v0.5.1, which predates the script.

After merge

Actions → MCP Registry → Run workflow on main, with tag v0.5.1.

Checks

  • Both workflow files parse as YAML. actionlint isn't installed here, so they are otherwise untested until they run.
  • wait-for-npm.sh flagrix 0.5.1 returns immediately. For a version that doesn't exist, it times out with an error.
  • The OIDC login and publish steps are copied unchanged from release.yml. In the v0.5.1 run the OIDC login passed, and the publish was refused only over the npm version (a 400, not a 403), so the namespace permission works.

…e-run

The v0.5.1 Release run published to npm, then sent server.json to the
MCP Registry a second later. The registry checks npm, which didn't serve
0.5.1 yet, and returned 400. The run can't simply be re-run, because
its npm publish fails on an existing version. A laptop
`mcp-publisher login github` can't publish under the flagrix-io
namespace either: that needs OIDC or a PAT with read:org.

- scripts/wait-for-npm.sh polls npm (the version document and the
  package's version list) for up to 15 minutes
- release.yml runs it between npm publish and the registry steps
- New mcp-registry.yml (workflow_dispatch, input: tag) publishes the
  tag's server.json over OIDC without touching npm; it checks the
  versions in server.json match the tag and waits for npm first
@tiltom tiltom self-assigned this Nov 10, 2026
@tiltom
tiltom merged commit 4dd345b into main Nov 10, 2026
3 checks passed
@tiltom
tiltom deleted the ci/mcp-registry-retry branch November 18, 2026 15:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant