v0.2.1: bump version, split changelog, fix v0.2.1 publish#8
Merged
Conversation
Original entry was written from the spec; missed several changes that landed during execution: registerTool migration with explicit titles, server.prompt(...) runtime registration, per-tool icons[] in tools/list, square 512×512 connector icon, language format correction (ISO 639-1 not 639-2), toolError body propagation, and the prompts[] manifest schema fix. Drops the "new square icon" deferred line — that did ship.
Three commits landed on main after v0.2.0 published to npm at bc4ac23: - de7645a (registerTool migration with explicit titles) - ab91a9a (square 512×512 connector icon) - 76720cf..67a0b9d (per-tool icons[] in tools/list — PR #7) Tag v0.2.1 was previously pushed at 97b297f but the publish workflow failed because package.json/manifest.json still said 0.2.0. This commit: - Bumps package.json + manifest.json to 0.2.1. - Splits the changelog so the v0.2.0 entry reflects what's actually on npm at v0.2.0, and a new v0.2.1 entry covers the three post-publish additions. After merge, retag v0.2.1 at the new HEAD to fire publish.yml.
Dev-vlad
changed the title
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.
Summary
Three commits landed on `main` after v0.2.0 was published to npm:
A `v0.2.1` tag was pushed earlier but the publish workflow failed at the version-match check because `package.json` and `manifest.json` still said `0.2.0`. The tag has been deleted (local + remote).
What this PR does
Test plan
After merge
```
git checkout main && git pull
git tag -a v0.2.1 -m "v0.2.1 — registerTool titles, square icon, per-tool icons[]"
git push origin v0.2.1
gh run watch -R joinmassive/mcp-server
```