Release 6.1.1-heyi.1 to main#17
Merged
Merged
Conversation
Back-merge main into dev — restore dev-first (dev was stuck at #10 / v6.1.1)
v6.2.0 hand-edited only the Claude manifests, leaving .codex-plugin, .cursor-plugin, .kimi-plugin, gemini-extension.json, and package.json at 6.1.1. Both Claude Code and Codex gate updates on the version STRING changing, so users installed at 6.1.1 never refreshed to the 6.2.0 claiming-protocol content. - Sync all 7 manifests via bump-version.sh onto an independent fork version line (6.2.0-heyi.1) that no longer collides with upstream. - Add a version-consistency check to fork-tests CI and a pre-commit hook so a future partial bump fails loudly. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017pGrJ7Ai49UYKFjKVshoXy
Fork the version line to 6.2.0-heyi.1 and guard drift in CI
With the -heyi.N suffix already identifying fork iterations, the numeric prefix no longer needs to be self-minted. Pin it to the actual upstream baseline (6.1.1, upstream's latest tag) so the version reads as a coordinate: <upstream-baseline>-heyi.<fork-iteration>. This drops the phantom 6.2.0 prefix (upstream has no 6.2.0; it was a leftover from reusing upstream's number line) and re-bases the fork line onto 6.1.1-heyi.1. Since 6.2.0-heyi.1 only ever reached dev, not main, no installed user is downgraded — this is a pre-release renumber. Also add docs/superpowers/versioning.md documenting the scheme: the prefix tracks upstream and is never self-minted, all fork changes ship as heyi.N increments, and the suffix resets to heyi.1 on each upstream sync. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017pGrJ7Ai49UYKFjKVshoXy
…eline Track upstream baseline in the version prefix (6.1.1-heyi.1)
Ship the fork version line (6.1.1-heyi.1) and the drift guard from dev to main so autoUpdate (Claude) and Codex / Cursor / Kimi / Gemini actually refresh users off the stale 6.1.1 / 6.2.0 content. Add the RELEASE-NOTES entry documenting the baseline-tracking version scheme and what this baseline carries. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017pGrJ7Ai49UYKFjKVshoXy
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.
Who is submitting this PR? (required)
claude-opus-4-8[1m]superpowers@superpowers-dev(this fork) +claude-plugins-officialset (commit-commands, code-review, context7, frontend-design, playwright, pr-review-toolkit, chrome-devtools-mcp, typescript-lsp, skill-creator, claude-md-management, ralph-loop)What problem are you trying to solve?
The fork version line and drift guard (#15, #16) are merged to
devbut notmain.mainstill ships6.2.0with the manifest drift, so Claude autoUpdate and Codex / Cursor / Kimi / Gemini users never refresh to the corrected, consistent content. Both harnesses gate updates on the version string changing, so nothing reaches users until a new string lands onmain(the marketplace source branch).What does this PR change?
Releases
devtomain: version6.1.1-heyi.1across all seven manifests, the CI + pre-commit drift guard,docs/superpowers/versioning.md, and a newRELEASE-NOTES.mdentry for6.1.1-heyi.1.Is this change appropriate for the core library?
Fork-internal release for
heyi-co/superpowers. Not proposed for upstream.What alternatives did you consider?
The version-scheme alternatives were weighed in #15 and #16 (self-minted line vs.
-heyi.Nsuffix vs. baseline-tracking prefix;-vs.+). This PR is purely thedev->mainrelease step for the chosen scheme.Does this PR contain multiple unrelated changes?
No. It releases the two already-reviewed version PRs (#15, #16) plus their release-notes entry — one concern: shipping the corrected version line to users.
Existing PRs
dev->mainpattern).Environment tested
claude-opus-4-8[1m]Verification:
bash scripts/bump-version.sh --check-> exit 0, all 7 manifests at6.1.1-heyi.1.fork-testsCI was green on both Fork the version line to 6.2.0-heyi.1 and guard drift in CI #15 and Track upstream baseline in the version prefix (6.1.1-heyi.1) #16 (includes the new version-consistency step).New harness support (required if this PR adds a new harness)
N/A — no new harness.
Evaluation
N/A — release + release notes, no behavior-shaping skill content modified.
Rigor
Human review