Skip to content

ci: wait for the npm version before publishing to the MCP registry - #7

Merged
dominik1001 merged 1 commit into
mainfrom
fix/registry-wait-for-npm
Nov 18, 2026
Merged

dominik1001 merged 1 commit into
mainfrom
fix/registry-wait-for-npm

Conversation

@dominik1001

Copy link
Copy Markdown
Owner

Problem

The first automated registry publish (run 44277350182) failed:

registry validation failed for package 0 (carddav-mcp): NPM package 'carddav-mcp' exists, but version '0.1.1' was not found (status: 404)

The mcp-registry job runs right after semantic-release, but npm made 0.1.1 visible only ~75s after semantic-release reported it published. Re-running the job a minute later succeeded, so this race would hit every release.

Change

publish-mcp-registry.yml polls npm view <pkg>@<version> every 15s (up to 10 min) before mcp-publisher publish. The package name comes from server.json.

Verification

YAML parses; the check returns immediately for a published version (0.1.1) and keeps waiting for a missing one. ci: only, so merging doesn't cut a release.

🤖 Generated with Claude Code

The 0.1.1 registry publish failed with 400 "version '0.1.1' was not found"
because it ran seconds after semantic-release published, while npm still
answered 404 (npm timestamped 0.1.1 ~75s after semantic-release reported
it published). Poll npm for up to 10 minutes first.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@dominik1001
dominik1001 merged commit 32538c0 into main Nov 18, 2026
10 checks passed
@dominik1001
dominik1001 deleted the fix/registry-wait-for-npm branch November 18, 2026 09:49
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