chore(release): v2.3.0#47
Merged
Merged
Conversation
Cut the v2.3.0 release: move the Command & Control + Impact corpus entries (14 red↔blue pairs, +28 files; corpus now 86 red / 85 blue) from [Unreleased] under the v2.3.0 heading. Merging to main triggers auto-tag.yml (tags v2.3.0 + publishes the GitHub Release) and sync-fanout.yml (opens the dotfiles-Kali companion.lock-bump PR to vendor the new corpus into offensive/companion/). Co-Authored-By: Claude Opus 4.8 <[email protected]> Claude-Session: https://claude.ai/code/session_012CpbBxJLgsg3T3ropqYGJA
Contributor
There was a problem hiding this comment.
Pull request overview
Cuts the v2.3.0 release by promoting the existing [Unreleased] changelog entry into a dated ## [v2.3.0] - 2026-07-10 section so the repo’s release automation can tag and publish the release from the topmost version heading.
Changes:
- Adds a new
## [v2.3.0] - 2026-07-10heading immediately after## [Unreleased]. - Leaves
[Unreleased]empty and associates the existing “Added” corpus entry with the newv2.3.0section.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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.
What
Cuts the v2.3.0 release. Moves the Command & Control + Impact corpus entries (14 new red↔blue pairs, +28 files — corpus now 86 red / 85 blue) out of
[Unreleased]under a dated## [v2.3.0] - 2026-07-10heading, leaving[Unreleased]empty. OnlyCHANGELOG.mdchanges.What merging this does
auto-tag.ymlreads the first## [vX.Y.Z]heading as the intended release. On merge tomainit will:v2.3.0tag and publish the GitHub Release (body carved from this CHANGELOG section).sync-fanout.yml, which opens the dotfiles-Kalicompanion.lock-bump PR to vendor the new corpus intooffensive/companion/.Both are idempotent no-ops if re-run — pushing
mainagain never double-tags.Version rationale
The only
[Unreleased]change is the corpus addition (feat) → minor bump from the currentv2.2.0→v2.3.0. No breaking changes.Verification
CHANGELOG.mdis the sole diff; theentries/tree is untouched, soci.yml's pairing / slot / drift gates are unaffected (they passed when the corpus merged in #46). The top version heading is now## [v2.3.0], which is whatauto-tag.shdetects.🤖 Generated with Claude Code
Generated by Claude Code