coops-mcp: bump to 0.1.1 for the first release under oceanmodeling - #125
Merged
Merged
Conversation
Metadata-only release. The wheel picks up the project URLs that now point at github.com/oceanmodeling/ocean-mcp (#120) and the README mcp-name marker io.github.oceanmodeling/coops-mcp (#123), and the registry step publishes the first entry under the org namespace. This is the canary for the transferred publish pipeline: it exercises the re-pointed PyPI trusted publisher and the org-owned registry namespace end to end before any other server is released.
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.
Why
First release since the repo moved to
oceanmodeling. Publishing is OIDC-bound to the repository owner, so this is the canary that proves the re-pointed PyPI trusted publisher and theio.github.oceanmodelingregistry namespace work end to end before any other server is released (transfer runbook, section 7).What
pyproject.toml:0.1.0->0.1.1server.json: bothversionfields ->0.1.1(same pattern as the ndbc/rtofs/winds bumps in ndbc-mcp: bump to 0.1.2, shorten server.json description under the registry's 100-char limit #112-winds-mcp: bump to 0.1.2, shorten server.json description under the registry's 100-char limit #114)No code changes. The published wheel picks up the project URLs from #120 and the README
mcp-namemarker from #123.After merge
Tag
coops-mcp-v0.1.1on the merge commit. Expected:publish.ymlgoes build -> test -> PyPI upload -> registry publish, PyPI shows 0.1.1, and the registry listsio.github.oceanmodeling/coops-mcp.Verification
Unit + protocol tests pass,
uv buildOK, ruff check/format clean.