Chore: Consolidate today's work back into one Unreleased section - #12
Merged
Conversation
The v0.2.1 and v0.3.0 releases created earlier today were rolled back (GitHub releases, packages, and tags all deleted) after a rebase orphaned the v0.3.0 tag's commit, causing axion to compute the wrong next version (0.2.1 instead of 0.3.1). Merges the [0.2.1] and [0.3.0] sections back into [Unreleased] so the next release starts clean from a single, correctly-ordered version bump. Also restored the Keep a Changelog/SemVer footer note, which had been silently dropped by the changelog plugin's patching (it only preserves versioned sections and the reference-link footer, not free-form prose between them).
There was a problem hiding this comment.
Pull request overview
This PR consolidates the prematurely-created v0.2.1 and v0.3.0 changelog entries back into a single [Unreleased] section, aligning the changelog with the rolled-back tags/releases and restoring the Keep a Changelog / SemVer footer note.
Changes:
- Merged the
0.2.1and0.3.0content back into[Unreleased]. - Restored the Keep a Changelog / Semantic Versioning explanatory footer text.
- Updated the
[Unreleased]compare link to start fromv0.2.0(sincev0.2.1/v0.3.0were rolled back).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
The manual consolidation matched the file's older hand-written style (no blank line between a header and its content), but the changelog plugin's own patchChangelog rendering always inserts one. Since the plugin will keep patching this file on every future release, match its style throughout (including the historical 0.2.0/0.1.0 sections) so future patches don't reintroduce a formatting diff.
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.
Summary
v0.2.1andv0.3.0releases created earlier today were rolled back (GitHub releases, packages, and tags deleted) after a rebase orphaned thev0.3.0tag's commit, causing axion to compute the wrong next version (0.2.1instead of0.3.1).[0.2.1]and[0.3.0]sections back into[Unreleased]so the next release starts clean from a single, correctly-ordered version bump instead of split across two premature releases.Test plan
./gradlew clean buildpasses./gradlew getChangelog --no-header --unreleasedconfirmed the consolidated Unreleased section reads back correctly with all entries intact