chore: bump version to 1.0.2#22
Merged
Merged
Conversation
Release the download_attachment annotation fix and complete tool-parameter descriptions (#21). Bumps every version reference for consistency, including two that had drifted: - package.json 1.0.1 -> 1.0.2 - package-lock.json (top-level + root package entry) 1.0.0 -> 1.0.2 (was never bumped for 1.0.1) - server.json top-level + npm package entry 1.0.1 -> 1.0.2 - src/index.ts McpServer({version}) 1.0.0 -> 1.0.2 (the server had been reporting 1.0.0 over MCP regardless of the published version) build, lint, format:check, and 366 tests pass. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
What
Version bump to 1.0.2 to release the tool-quality work from #21 (download_attachment annotation fix + complete tool-parameter descriptions).
Updates every version reference for consistency — including two that had drifted out of sync in prior releases:
package.jsonpackage-lock.json(top-level + root entry)server.json(top-level + npm package entry)src/index.tsMcpServer({version})The lockfile and the
McpServerversion had never been bumped past 1.0.0, so the running server was advertising1.0.0over MCP regardless of the published npm version. This fixes that.Verification
npm run build(built artifact reportsversion: "1.0.2"),npm run lint(0 errors),npm run format:check, and 366 tests all pass.Release sequence (after merge)
v1.0.2onmain→ triggerspublish.yml(npm publish with provenance).server.jsonto the MCP Registry (mcp-publisher publish).🤖 Generated with Claude Code