Skip to content

fix: stop replaying release notes at TUI startup - #156

Merged
jefft72 merged 1 commit into
mainfrom
codex/fix-whats-new-persistence
Aug 30, 2026
Merged

jefft72 merged 1 commit into
mainfrom
codex/fix-whats-new-persistence

Conversation

@jefft72

@jefft72 jefft72 commented Aug 30, 2026

Copy link
Copy Markdown
Contributor

Summary

Fixes a startup regression where reopening the Diffex TUI repeatedly displayed the welcome preview and the complete inherited changelog even after the notes had already been acknowledged.

Reasoning

The CLI package version was reset to 0.2.0 while the inherited changelog begins at 0.84.0, so semantic-version comparison permanently classified the historical archive as newer.
Tracking the acknowledged entry by changelog document order handles version resets safely while preserving future release-note behavior.

Changes

  • Tracks startup changelog acknowledgement using document order instead of package semver
  • Baselines fresh installs and unknown legacy markers without replaying historical notes
  • Shows the welcome preview only for entries that are actually unseen
  • Adds regression coverage for version resets, legacy markers, and repeated launches

Testing

  • npm run check
  • npm run build:offline
  • npm exec -- tsgo --noEmit
  • npm exec -- vitest run packages/coding-agent/test/changelog.test.ts - 6 passed
  • Launched the built TUI twice with the same persisted profile and verified both launches omitted historical notes
  • Full coding-agent suite: 2,354 passed; 2 pre-existing compaction assertion failures remain unrelated to this diff

Track startup release notes by changelog document order rather than package semver so version resets do not replay inherited history. Baseline fresh and legacy markers at the current changelog head and only preview entries that are actually unseen.
@jefft72 jefft72 self-assigned this Aug 30, 2026
@jefft72
jefft72 merged commit 129b5ad into main Aug 30, 2026
0 of 3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant