Repository navigation
ci: Trusted Publishing + MCP Registry - #71
Merged
Merged
Conversation
…gistry - Exchange the job OIDC identity for a publish credential (no NPM_TOKEN) - Update npm to >= 11.5.1, keep provenance and run tests before releasing - Migrate server.json to the 2025-10-17 schema and add mcpName to package.json - Sync server.json version on release and chain the MCP Registry publish - Run CI on the development branch too
ci: publish to npm with Trusted Publishing and register in the MCP Registry
|
🎉 This PR is included in version 2.7.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
Lleva a
mainla migración de #70. Solo cambia CI, así que no genera release: la próximafix/featpublicará por OIDC y dará de alta el paquete en el MCP Registry.🤖 Generated with Claude Code