Freeze CHANGELOG.md; git history is the changelog now - #71
Merged
Conversation
puppetsync has no versioned releases (the 17 existing tags are Jira-session markers from 2021-2022), so per-PR changelog entries had no release to collect them and turned every in-flight PR into a merge conflict with every other. - Add a freeze notice: ongoing history lives in the git log and merged PRs, whose squash-merge titles serve as the changelog - Convert the [Unreleased] section into dated sections using the dates each entry was recorded (from git blame): 2026-07-29 (the recent modernization: simp#49, simp#51-simp#54), 2023-08-03, and 2023-04-17 - Drop the dangling [Unreleased] reflink; keep all historical sections - Retire rakelib/keep_a_changelog.rake (release tooling for the Jira-tag era; no remaining consumers) - Update AGENTS.md's session checklist accordingly Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
silug
added a commit
to silug/simp-puppetsync
that referenced
this pull request
Jul 30, 2026
CHANGELOG.md is frozen (see simp#71); the squash-merge PR title carries this change's history. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
silug
added a commit
that referenced
this pull request
Jul 30, 2026
CHANGELOG.md is frozen (see #71); the squash-merge PR title carries this change's history. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
silug
added a commit
to silug/simp-puppetsync
that referenced
this pull request
Jul 30, 2026
CHANGELOG.md is frozen (see simp#71); the squash-merge PR title carries this change's history. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
nick-markowski
approved these changes
Jul 30, 2026
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
2 participants
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.
puppetsync has never had a versioned release — the 17 existing tags/GitHub releases are Jira-session markers from 2021–2022 (
SIMP-10633was the last, March 2022). With no release event to collect entries, per-PRCHANGELOG.mdedits to the shared[Unreleased]section were pure conflict surface: every open PR collided with every other.Changes
Subject (#NN)) serve as the changelog — always current, never conflicts, linked to full diff and discussion.[Unreleased]converted to dated sections using the date each entry was recorded, pergit blame:2026-07-29(the recent modernization: Full idempotency: repos that need no changes must pass through cleanly #49, Remove GitLab remnants; stop requiring GITLAB_API_TOKEN on every run #51–Add CI for puppetsync itself (unit tests for tasks, plan smoke test) #54, the dash fix),2023-08-03, and2023-04-17. All Jira-era historical sections retained as-is.[Unreleased]reflink dropped.rakelib/keep_a_changelog.rakeretired — it was release tooling for the Jira-tag era ([Unreleased]→tag conversion) with no remaining consumers.Once this merges, #69's changelog hunk gets dropped and it comes out of draft.
If versioned releases ever materialize (Forge/gem publication, Sicura-branded tooling), Release Drafter or similar can be added then — with actual tags and a consumer to justify it.
🤖 Generated with Claude Code