Skip to content

Use uniform release headers in CHANGES.md - #155

Open
fingolfin wants to merge 2 commits into
masterfrom
changes-md
Open

fingolfin wants to merge 2 commits into
masterfrom
changes-md

Conversation

@fingolfin

Copy link
Copy Markdown
Member

This renames CHANGES to CHANGES.md and 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.g at 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

The next commit makes its release headers uniform.

Assisted-by: Claude Code (Opus 5.5)
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

codecov Bot commented Oct 1, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 54.52%. Comparing base (41943e0) to head (fd4f781).

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #155   +/-   ##
=======================================
  Coverage   54.52%   54.52%           
=======================================
  Files         109      109           
  Lines       40334    40334           
  Branches     2353     2353           
=======================================
  Hits        21993    21993           
  Misses      18043    18043           
  Partials      298      298           
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant