Repository navigation
docs(changelog): match evo.polaris's changelog format with no date on version headings - #99
Merged
Merged
Conversation
… version headings
Kelly, 2026-10-27: every repo's changelog should match evo.polaris's
CHANGELOG.txt, newest first, and "no need to include when deployed".
zbump cuts a release as zdeploy deploys, so the date on a version
heading was the deploy date; the tag still carries it.
- 12 version headings lose their date: "## v..." and nothing after.
- scripts/plaintext_twins.py underlines a third-level heading with ~, as polaris's
md-txt.mjs does, so a release's Added / Fixed groups read as a level
below its version in the .txt twin. Every twin is regenerated;
2 other twin(s) change only in that underline.
- The intro now opens with polaris's sentence ("Notable changes to the
evomedia.net Token Savers, newest first.") and gains polaris's
five-parts paragraph. It does not claim every entry links a pull
request, because these entries are written by hand.
- This change's own line under Unreleased.
Co-Authored-By: Claude Opus 5.5 <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
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 and why
Kelly, 2026-10-27: every repo's changelog should match evo.polaris's
CHANGELOG.txt, newest first, and "no need to include when deployed". zbump cuts a release as zdeploy deploys, so the date on a version heading was the deploy date. The annotated tag still carries it.## v0.0.1.0.23 - 2026-10-23becomes## v0.0.1.0.23. Nothing else in a section changes.scripts/plaintext_twins.pyunderlines a third-level heading with~, exactly as polaris'smd-txt.mjsdoes, so a release's Added / Fixed groups read as a level below its version in the.txttwin. Every twin is regenerated with the repo's own tool; 2 other twin(s) change only in that underline.Group order already matched polaris's (Added, Changed, Fixed, Documentation, Maintenance) in every section, so no entries moved.
Keeping it this way
zbump still writes a dated heading at each release until evo.scripts#234 merges. After that it writes the version alone. Merge that one first, or the next release here puts a date back.
Tests
python scripts/plaintext_twins.py --check: in sync.tests/PlainTextTwins.Tests.ps1: 3 passed.Changelog and twins only. Nothing to deploy.
🤖 Generated with Claude Code