Repository navigation
fix(release): wait three hours for the npm package before listing sysml-mcp - #1338
Merged
Merged
Conversation
…ml-mcp The MCP Registry workflow starts when the tag is pushed, but CircleCI's publish-npm job publishes @openmbee/sysml-mcp only after the suite and the GitHub release: the v0.10.0 and v0.10.1 tags reached npm 84 and 72 minutes after tagging, past the script's one-hour wait, so the first listing would have failed. Raise the default wait to three hours and the job timeout to match, and record on the npm page that a package the release creates needs the nightly registered as a trusted publisher before the nightly can publish it. Co-Authored-By: jason.han <hanhuijun@gmail.com>
Contributor
Author
|
I'll fix CI failures and address comments from users with write access. I'll skip comments containing "(aside)".
|
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
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
1 participant
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.
What and why
The MCP Registry workflow (
.github/workflows/mcp-registry.yml) starts the moment av*tag is pushed, but the npm package it lists,@openmbee/sysml-mcp, is published by CircleCI'spublish-npmjob only after the suite and the GitHub release.scripts/mcp-registry-publish.shwaited for the package for at most one hour (MCP_REGISTRY_NPM_TIMEOUTdefault 3600), inside a 90-minute job. The last two releases took longer than that to reach npm: thev0.10.0tag was created at 2026-10-11T19:35Z and@openmbee/opensysml@0.10.0appeared at 20:59Z (84 minutes);v0.10.1at 2026-10-16T01:52Z and0.10.1at 03:04Z (72 minutes). So the first listing, on the next release tag, would have failed with "not on registry.npmjs.org after 3600s" before the package existed.scripts/mcp-registry-publish.sh: default wait 3600 → 10800 seconds..github/workflows/mcp-registry.yml:timeout-minutes90 → 200, so the job outlives the wait.docs/project/releasing.md: the registry section states the new wait and why; the npm section records that a package the release creates (the six@openmbee/sysml-mcp*packages ship this way first) needs the nightly registered as a trusted publisher on npmjs.com before the nightly can publish it — the nightly'snpm publishof a never-published package fails with404 Not Found - PUT, which is what the 2026-10-20 nightly's npm job did.No changelog fragment: the change is to the release pipeline and its maintainer documentation, nothing a user of a release sees.
How it was verified
scripts/mcp-registry-publish.sh --check v0.11.0still validates the filledserver.json(mcp-publisher 1.8.1, installed byscripts/install-mcp-publisher.sh).go test -count=1 -run 'TestMCPRegistry|TestNightly' ./tests/hygienepasses.python3 scripts/check-doc-ids.pyandpython3 scripts/changelog.py checkpass.git for-each-refon the tags andnpm view @openmbee/opensysml time.Checklist
make testandmake lintpass locally (hygiene suite and the doc checks that cover these files)changes/unreleased/<slug>.<section>.md, not as an edit toCHANGELOG.md(not user-visible)make docs-countsrun if a gate count moved (no gate count moved)F4,K5) in the body, docs, or changelogLink to Devin session: https://nasa-jpl-demo.devinenterprise.com/sessions/3340be9bab3547ee882933bc84a36cea
Open in Devin Desktop: https://nasa-jpl-demo.devinenterprise.com/desktop/session/3340be9bab3547ee882933bc84a36cea?variant=devin
Requested by: @HuiJun