Add changelog #71
Labels
No labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Grandiras/Ponente#71
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Add a changelog, that feeds a simple modal dialog when clicked (simple sparkle or similar in the header when a new version is now used). Ensure the changelog is simple and easy to understand for non-technical users.
🤖 On it — follow along in the action run; the reply will link the full session transcript.
📜 Live transcript — updating every ~5 minutes while the task runs.
Pushed. Final summary:
Added a changelog and the "What's new" dialog it feeds, on branch
claude/issue-71.What a member sees. When the version on screen is one their browser hasn't read about, a sparkle appears in the header. Clicking it opens a dialog: one block per release, the date as the heading, the version as a footnote beside it, and a few bullets written for somebody who has never read the code. The entry that was new is marked while it's being read. Once opened, the sparkle is gone for good and What's new stays in the nav menu — which is also the one place in the app that names the running version, for a bug report.
Three decisions worth flagging.
Services/Changelog.cs, and deliberately noCHANGELOG.mdbeside it. Two lists of the same releases drift, and the one that drifts is the one nobody has open while writing code. So the entry is part of the change rather than part of the tag — written in the PR that makes the change, dated the day it lands. The release skill now checks before tagging thatChangelog.Latest.Versionis the version about to be cut.Translationsis, falls back to English by the same rule, andChangelogTestsre-imposes the same guards — both languages, nothing blank, no "handle" — plus a jargon guard, because this is the one piece of copy whose failure mode is sounding like a commit message.Member.HasUnseencompares for equality rather than order, so a rollback announces itself too.I backfilled entries for 1.0.0 through 2.3.0 from the git history, and wrote 2.4.0 for what has landed since 2.3.0 (boards, board sharing, the general calendar, phone drag, this dialog). 2.4.0 is what this should ship as — the entry names that version, so tagging anything else would leave it announcing a release that never existed.
One trap the suite caught: excluding
.nav-whatsnewfrom.board-user button:not(.nav-hamburger)adds a second:not(), which raises that selector above.board-user .nav-pref-options buttonand paints a surface over the theme pills — all three then read as chosen.prefs.spec.jsfailed on it; the icon button overrides those defaults from its own block instead, the way.nav-menu-installdoes.Verified (no container engine in this runner, so I installed the .NET 10 SDK and Postgres and ran the app directly on
:8090in Development):dotnet test Ponente.sln— 205 passing, 9 new.changelog.spec.jspasses, plusprefs,install,i18n,board,mobile,filter,boards,calendar-all,auth-entrance,board-entrance,reconnect,icons.boards.spec.js"the nav switches boards",calendar.spec.js"a six-week month fits a short window") — I confirmed both fail identically on unmodifiedmainhere, so they're environmental, not from this change.access.spec.js/pds.spec.jsweren't run: no PDS container.⏱ 21m 27s · 114 turns · tokens: 186.9k in / 53.4k out (+14780.8k cache-read)
📜 Full session transcript
→ Opened PR: #90