ci: enable npm auto-publish + fix MCP Registry description length - #49
Merged
Merged
Conversation
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.
Two release-automation fixes:
server.json— shortendescriptionto ≤100 chars (the MCP Registry rejects longer). The registry entryio.github.argon-lab/argonis already live at v2.0.1; this syncs master so future release-triggered publishes don't fail validation.release.yml— enable thepublish-npmjob so a tag push auto-publishesargonctlto npm.Action required to activate #2: add an
NPM_TOKENrepo secret — an npm Automation token (or granular with 2FA bypass) that ownsargonctl, so CI publishes without an OTP:After that, cutting a release ( bump version → tag
vX.Y.Z) auto-builds binaries and publishes npm; then run thepublish-mcpworkflow (or dispatch it) to register the new version.