chore(deps,ci): vitest 4.x + decouple MCP Registry publish#49
Merged
Conversation
…lish - Bump vitest / @vitest/coverage-v8 to 4.x. Clears the 6 remaining dev-only high advisories (vitest/vite/vite-node/@vitest/mocker/esbuild chain). npm audit now reports 0 vulnerabilities across dev + prod. No shipped change — dev deps don't reach npm consumers; full 1402-test suite green on vitest 4 (5 pre-existing env-only failures unchanged). - publish-mcp.yml: MCP Registry job no longer hard-depends on npm-job success (`if: !cancelled()`). A failed npm publish (EOTP on manual-token releases) no longer blocks the registry update; re-run via workflow_dispatch after a manual npm publish. No version bump: dev-dependency + CI maintenance only. 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.
Maintenance follow-up к 0.46.0. Версию не бампаю — меняются только dev-deps + CI, в npm-пакет ничего не уходит (dist идентичен).
vitest → 4.x
Закрывает оставшиеся 6 dev-only high advisories (цепочка vitest/vite/vite-node/@vitest/mocker/esbuild). После бампа:
npm audit= 0 уязвимостей (dev + prod)..mcp.jsonрабочей папки; index.test.ts git-root — флэйк субпроцесса под параллельной нагрузкой), не от vitest 4.MCP Registry decouple
publish-mcp.yml: mcp-job больше не зависит от успеха npm-job —if: ${{ !cancelled() }}. Падение npm-publish (EOTP на ручном токене) больше не блокирует обновление регистра. Порядок сохранён (npm первым на happy-path); регистр валидирует npm-версию независимо, так что ручнойnpm publishего удовлетворяет. После ручной публикации — перезапуск job черезworkflow_dispatch.Не входит (по твоему «автопаблиш не надо ещё»)
npm CI авто-публиш (Automation token +
mfa=automation) — отложено.🤖 Generated with Claude Code