Skip to content

CHANGELOG.md retired: the release notes are the pull request titles - #58

Merged
apostasie merged 1 commit into
mainfrom
claudio/20261008-drop-changelog
Oct 8, 2026
Merged

apostasie merged 1 commit into
mainfrom
claudio/20261008-drop-changelog

Conversation

@closer-claudio

Copy link
Copy Markdown
Contributor

🎯 Why

limen v0.9.0 C4: a repository with a populated [Unreleased] cut its next release under the old scheme first (dot 1.2.0, tagged), then deletes CHANGELOG.md; release notes are the merged pull request titles from here on.

🛠️ What

  • CHANGELOG.md deleted (its history stays in git: git show v1.2.0:CHANGELOG.md).
  • README.md, Releasing: the notes are the pull request titles, published on the tag's release page with gh release create vX.Y.Z --verify-tag --generate-notes (dot has no release workflow); a breaking pull request carries the breaking label.

🧪 How

  • V: just lint and just test green.
  • 📝 v1.2.0 has no release page yet; Manager has it.

limen v0.9.0 C4, after 1.2.0 shipped under the hand-written file. From
here a release's notes are the titles of the pull requests it merged,
published on the tag's release page with the generated notes, and a
pull request that breaks a consumer carries the `breaking` label. The
README's releasing paragraph says so instead of naming the file; its
history stays in git.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Signed-off-by: closer-claudio <claudio@farcloser.world>

@closer-claudio closer-claudio left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ at 7017e6c: CHANGELOG.md goes after the v1.2.0 tag, and the README says where the notes live now.

🔍 Checked: v1.2.0 is tagged (no release page yet, as the body says); every .md/.yaml/.just/.toml/.json/.sh at this head grepped for "changelog" — the one hit is AGENTS.md's own "no CHANGELOG.md is kept by hand", which this PR makes true; nothing links to the file. The README's gh release create vX.Y.Z --verify-tag --generate-notes is the step limen#298 puts in just do release (with --notes-start-tag, -R and --prerelease on top), so the two agree. One commit on current main (877fa0d).

📝 Until the limen bump carrying #298 lands here, the v1.2.0 page is a hand step; when it is made, --notes-start-tag v1.1.1 keeps it to the one release, since no earlier tag has a page.

@apostasie
apostasie enabled auto-merge October 8, 2026 07:22
@apostasie
apostasie merged commit 2da798e into main Oct 8, 2026
12 checks passed
@apostasie
apostasie deleted the claudio/20261008-drop-changelog branch October 8, 2026 07:27
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.

2 participants