Bump version to 1.0.10 - #68
Merged
Merged
Conversation
v1.0.9 was tagged without a version bump, so the publish workflow's tag/package.json guard failed and nothing was released. Skipping to 1.0.10 rather than moving the already-pushed v1.0.9 tag. Assisted-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Signed-off-by: Sergey Vilgelm <sergey@vilgelm.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
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 v1.0.9 tag was pushed without a corresponding version bump, so the publish workflow stopped at its tag/package.json guard (
package.json version (1.0.8) does not match git tag (1.0.9)) and nothing reached npm —latestis still 1.0.8. The guard worked as intended; there is nothing to roll back.This bumps the three places that have to move together —
package.json,package-lock.json, and theMcpServerliteral insrc/main.ts— going to 1.0.10 rather than moving the already-published v1.0.9 tag, so no public ref gets rewritten. v1.0.9 stays a dead tag.Verified locally: the workflow's version guard passes against a v1.0.10 tag, fmt:check / lint / build are green, and a production
npm pack --dry-runconfirmsdist/plugin.zipis in the tarball (the packaging trap that broke v1.0.0 and v1.0.1).Once this merges, tagging v1.0.10 on the merge commit will trigger the release.