Repository navigation
Use uniform release headers in CHANGES.md - #61
Merged
Merged
Conversation
Start each release entry with `## VERSION (YYYY-MM-DD)`, newest first, so that scripts can extract the release notes. Missing or partial dates are taken from the git history. Assisted-by: Claude Code (Opus 5.5)
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #61 +/- ##
=======================================
Coverage 82.28% 82.28%
=======================================
Files 2 2
Lines 4065 4065
=======================================
Hits 3345 3345
Misses 720 720 🚀 New features to boost your workflow:
|
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.
This starts each release entry with a uniform header,
## VERSION (YYYY-MM-DD). We are moving the changelogs of the packages in gap-packages to this format, so that scripts can extract the notes of each release.Dates missing from the file, or given only as a month, are taken from the git history: the date in
PackageInfo.gat the release tag, or the date of the tagged commit. Where neither exists, the entry keeps its month (YYYY-MM) or has no date. Otherwise only headers and formatting change: indentation, blank lines, separator lines and list markers.🤖 Generated with Claude Code