Cut 1.3.0 release - #9
Merged
Merged
Conversation
Move the [Unreleased] batch (sd:release command, validate scripts, CI, uninstaller, command/agent refinements) into [1.3.0] - 2026-06-18 and add the missing [1.2.0] and new [1.3.0] compare-link footers. Relax validate Check 6: an empty [Unreleased] now passes when it sits directly above a dated [x.y.z] release (the just-cut state); a non-release empty section still fails, preserving the per-PR changelog invariant. 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
Cuts the 1.3.0 release. Moves the accumulated
[Unreleased]batch into a dated[1.3.0] - 2026-06-18section and fixes the changelog compare-link footers.Per SemVer + the repo's own bump rule (any feature -> minor), this is
1.2.0 -> 1.3.0: the batch adds new features (/sd:releasecommand,validatescripts, CI workflow, uninstaller) plus the command/agent refinements.Changes
CHANGELOG.md[Unreleased]batch ->[1.3.0] - 2026-06-18with a one-line release summary.[1.2.0]compare link (never added when 1.2.0 shipped) and the new[1.3.0]link; repointed[Unreleased]tov1.3.0...HEAD.scripts/validate.ps1+scripts/validate.sh(lockstep)[Unreleased]passes only when the section directly below it is a dated[x.y.z] - <date>release (the just-cut state). A non-release empty section still fails, preserving the "every PR adds a changelog line" invariant.Verification
validate.ps1full run: all 6 checks pass, exit 0 (ASCII scan included).🤖 Generated with Claude Code