chore(release): bump MCP package to 0.0.9 - #678
Merged
Conversation
0.0.8 is already on npm. The WALM-321 cold-start fix landed on dev after that publish and was appended under the 0.0.8 heading. Move those notes to a new 0.0.9 section and bump every MCP/plugin manifest so the next publish is a real release, not a rewrite of a shipped version. Also point the manual release verifier at SDK 0.1.3, which is already on dev.
Collaborator
Style Guide AuditAll 1 file(s) pass the style guide audit. |
harrymove-ctrl
approved these changes
Aug 18, 2026
Merged
harrymove-ctrl
pushed a commit
that referenced
this pull request
Aug 18, 2026
Follows the manual release flow used by #678, not changesets: bump every MCP/plugin manifest together, add the version section to both changelogs, and move the verifier's expected version forward. `verify-manual-sdk-release.mjs` reports "MCP package 0.0.10: manifests and changelogs synchronized". Drops the changeset added earlier in this PR. Leaving it alongside a manual bump would have double-bumped on main, since release-mcp.yml runs `changeset version` there and would have taken 0.0.10 to 0.0.11 while rewriting the changelog section added here. Replaces the review request on #681 for a changeset or changelog update.
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
3 participants
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
@mysten-incubation/memwal-mcp@0.0.8is already on npm (2026-08-14). The WALM-321 cold-start fix (#579) landed ondevafter that publish and was appended under the 0.0.8 heading.This is the missing manual version bump:
0.0.8→0.0.9in every MCP / plugin manifest (same set as the 0.0.8 release).## 0.0.9changelog inpackages/mcp/CHANGELOG.mdanddocs/mcp/changelog.mdx.TESTING.mdpins updated to0.0.9-dev.N/latest= 0.0.9 aftermain.Also syncs
scripts/verify-manual-sdk-release.mjsto SDK 0.1.3 (already ondev) so the checker matches the tree.No code change. OpenClaw stays 0.0.5.
Why a separate PR
#677 (
dev→staging) should not carry a version bump of its own. Merge this todevfirst; #677 will pick it up automatically.After merge
release-mcp.ymlshould publish@mysten-incubation/memwal-mcp@0.0.9-dev.Non thedevdist-tag.lateststays 0.0.8 until this reachesmain.