Repository navigation
ci: wait for npm before the MCP Registry; add a registry-only workflow - #10
Merged
Merged
Conversation
…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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The v0.5.1 Release run (42884948030) published
flagrix@0.5.1to npm. About a second later it sentserver.jsonto 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 publishwould fail on the version that now exists. Publishing from a laptop doesn't work either.mcp-publisher login githubonly grantsio.github.tiltom/*, and theio.github.flagrix-ionamespace needs GitHub Actions OIDC or a classic PAT withread: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.ymlruns it betweennpm publishand the registry steps.mcp-registry.yml(manual, inputtag) publishes the tag'sserver.jsonto the registry over OIDC without touching npm. It checks that both versions inserver.jsonmatch the tag and waits for npm before publishing. It checks out the branch it is run from and readsserver.jsonfrom the tag, so it also works forv0.5.1, which predates the script.After merge
Actions → MCP Registry → Run workflow on
main, with tagv0.5.1.Checks
actionlintisn't installed here, so they are otherwise untested until they run.wait-for-npm.sh flagrix 0.5.1returns immediately. For a version that doesn't exist, it times out with an error.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.