Add CHANGELOG#31
Draft
etagwerker wants to merge 1 commit into
Draft
Conversation
Closes #25 Introduce a CHANGELOG.md following the Keep a Changelog format, documenting the 2.0.x release line of the standalone gem. 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
Adds a
CHANGELOG.mdto the repo, closing #25.Why
The issue asks for a changelog so it's easier to track what changed between released versions. Until now you had to read through git history or compare tags to figure out what shipped.
How
The changelog follows the Keep a Changelog format and Semantic Versioning. It documents the standalone gem's
2.0.xline (this repo was split out of the maindatabase_cleanerrepo atv2.0.0.beta), reconstructed from tags and commit history:Unreleased(CI pivot to GitHub Actions)2.0.2,2.0.1,2.0.0,2.0.0.betaEach entry is grouped under Added / Changed / Fixed and links to the relevant PR where one exists. Version headings link to GitHub compare views.
Notes
Opening as a draft. A couple of things worth a second look:
2.0.xline since that's when this gem became standalone. Should the older0.x/1.xtags (inherited from the combined repo) be included too, or is starting at2.0.0.betathe right call?Unreleasedsection maintained as part of the release process, or do you prefer generating entries at release time?Closes #25
🤖 Generated with Claude Code