Rename package to @evalops/mcp-openapi; add npm publish to release workflow - #41
Merged
Merged
Conversation
…rkflow The unscoped "mcp-openapi" name on npm is owned by an unrelated third party, so this package can never publish under it. Rename to @evalops/mcp-openapi (bin name stays "mcp-openapi"), add license, repository, keywords, and publishConfig fields, and bump to 0.5.0 since the rename is breaking for library consumers. The release workflow now publishes to npm with provenance on tag pushes when the NPM_TOKEN repository secret is configured; without the secret the publish step is skipped and the GitHub release still happens. Scaffolds emit "@evalops/mcp-openapi": "github:evalops/mcp-openapi" so the dependency key matches the package's real name. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LqBsGC7xLvihtBxhCdWKz5
This was referenced Aug 4, 2026
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.
The unscoped
mcp-openapinpm name is owned by an unrelated third party (docat0209, v0.3.0), so this project can never publish under its current name. This PR:@evalops/mcp-openapi; themcp-openapibin name is unchanged. Version bumped to 0.5.0 (rename is breaking for library consumers).license,repository,homepage,bugs,keywords,publishConfig.access=publicto package.json.v*tags) now runsnpm publish --provenancewhen theNPM_TOKENrepo secret is set; skipped otherwise, GitHub release unaffected.id-token: writeadded for provenance.init/generatescaffolds emit the dependency under the key@evalops/mcp-openapiso it matches the package's real name.Action needed to actually publish (cannot be done from this session — no npm credentials on this machine): create an npm automation token for the
@evalopsscope, add it as theNPM_TOKENrepo secret, then push av0.5.0tag.Gates: check/test/pack pass locally;
npm packproducesevalops-mcp-openapi-0.5.0.tgzwith the expected metadata.🤖 Generated with Claude Code
https://claude.ai/code/session_01LqBsGC7xLvihtBxhCdWKz5