Changelog for 2.8.0 #228
No reviewers
Labels
No labels
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Grandiras/Ponente!228
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "release/v2.8.0"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This moves the Unreleased changelog block into a 2.8.0 release dated today and leaves an empty block for the next cycle. The
v2.8.0tag goes on this PR's merge commit.What 2.8.0 contains, since v2.7.0:
Why a minor: two changes a member will notice, no migration, and no new configuration.
check-env-keys.shpasses for both prod and dev, and production follows:latest(not pinned).🤖 Generated with Claude Code
🤖 Reviewing this PR — the review will link the full session transcript.
📜 Live transcript — updating every ~5 minutes while the review runs.
✅ Verdict: approve — no blocking issues found.
Correct and complete release promotion. The 2.8.0 entry is byte-for-byte what
promote-changelog.pywrites: the whole Unreleased block promoted intoReleasesat the top (newest first), dated the day thev2.8.0tag is cut, with a fresh emptyUnreleasedblock that still names both locales soChangelog.For's English fallback never loses a key. The two bullets match the member-visible changes since v2.7.0 (#224, #225/#227), bold markers pair asChangelogTestsrequires, and nothing else in the repo hard-codes the version. Minor: 2.8.0 and 2.7.0 now both carry 2026-09-23 — pre-existing on main, not introduced here, and harmless if both were cut the same day.⏱ 0m 35s · 6 steps · $0.0097 · tokens: 48.5k in / 1.2k out (+51.3k cache-read) · Go: 5h 16% · wk 80% · mo 73%
📜 Full session transcript