ci: publish workflow does MCP Registry only (drop doomed npm job)#50
Merged
Conversation
The org's npm account enforces 2FA/OTP, which a CI token can't satisfy, so the npm job failed with EOTP on every release and marked the whole Publish run red even though the MCP Registry job succeeded. npm is published manually; the CI npm job was vestigial. Remove the npm job entirely. The workflow now only publishes to the MCP Registry (sync server.json → OIDC login → publish), so the run is green when the registry publish succeeds. Run it after the manual `npm publish` (tag push or workflow_dispatch); the registry validates the npm version exists. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Проблема
npm-аккаунт орги требует 2FA/OTP — CI-токен это не может, npm-job падал
EOTPна каждом релизе и красил весь Publish-run в red, хотя mcp-job отрабатывал. npm публикуется руками → CI-шный npm-job был бесполезным.Фикс
Убран npm-job целиком. Publish-workflow теперь делает только MCP Registry (sync server.json → OIDC login → publish). Run зелёный, когда регистр опубликовался. Запускать после ручного
npm publish(push тега или workflow_dispatch); регистр сам валидирует, что npm-версия существует.Снимает постоянный красный ❌ на publish-прогонах. CI (тесты) не затронут.
🤖 Generated with Claude Code