chore: bump to v0.1.5 + tighten MCP SDK label in README - #1
Merged
Conversation
- README.md: match line 458's SDK reference to line 20's — drop "SDK v2" suffix so both references read "MCP TypeScript" for consistency. - package.json 0.1.4 → 0.1.5 - manifest.json 0.1.4 → 0.1.5 (parity enforced by scripts/pack-mcpb.mjs) First real use of the PR flow now that branch protection is in place — this branch will be merged into main via GitHub PR, then a v0.1.5 tag push from main will trigger the split release pipeline (release-mcpb + release-npm in parallel). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Two changes on the PR branch:
1. Automate the tag step. release.yml now triggers on push to main
(instead of tag push) and auto-detects a version bump by comparing
package.json's version against existing tags. New workflow shape:
detect (read version, check tag exists)
└─> gate (full CI)
└─> tag (git tag vX.Y.Z && git push)
├─> release-mcpb (parallel — .mcpb + .zip to GitHub Release)
└─> release-npm (parallel — npm publish via OIDC)
When main advances without a version bump, `detect` sets
should_release=false and every downstream job skips. Removes the need
for a manual `git tag && git push` after each merge — the merge itself
is now the release trigger.
2. Delete the `docs/` folder (internal superpowers specs and plans that
were only relevant to project setup) and its lone README reference.
Full local gate green: typecheck, lint, spellcheck, 218/218 tests.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Removes the tracked pre-commit hook wrapper. Husky itself remains in devDependencies (the prepare script still initializes .husky/_/ locally on npm install), but the folder is now ignored — no repo-wide pre-commit hooks are enforced, and each developer can opt in if desired. Quality still runs at CI time (typecheck, lint, spellcheck, audit, tests) via .github/workflows/ci.yml on every push and PR, so nothing broken lands on main. Also fixes a .gitignore trailing-newline glitch where an earlier "dist/*.zip" entry got concatenated with the new ".husky/" line. Co-Authored-By: Claude Opus 4.7 (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.
Summary
Context
First real use of the PR flow after enabling branch protection on `main`. Once merged, tagging `v0.1.5` on main will fire the split release pipeline (`release-mcpb` and `release-npm` in parallel).
Test plan
🤖 Generated with Claude Code