[sedax90]

Summary

• The first launch of a newer release shows a toast, "TablePro was updated to ". Its What's New button opens the About dialog, whose What's New page lists that release's notes from the metainfo, translated.
• The newest release that ran is kept in a new GSettings key, last-seen-version, compared by semver.
• A first install, the same version again and a development build say nothing.
• A downgrade says nothing and leaves the newer version stored (linux/docs/releasing.md, Downgrades). Before, it said "updated to" the older version and overwrote the newer one.
• The toast shows only when the About dialog has notes for that version, and only once the version is recorded, so it never repeats.
• The button uses the toast's own action-name (app.about) instead of a closure.
• The crash notice and the update notice are one LaunchNotice enum with one hand-over path. Each stays on every page the window shows (picker, connecting, workspace) until dismissed, and a new notice replaces only its own kind.
• linux/docs/storage.md lists the new key.
• macOS: the Welcome window's What's New link had the same downgrade defect. It now records CFBundleVersion in lastSeenAppBuild, the number Sparkle orders updates by, so a beta sorts below its stable. An older build shows nothing and writes nothing. A Mac that recorded only the version before carries it over once.
• iOS: What's New had the same defect after installing an older TestFlight build. Versions now compare as numbers, which the App Store's integer-only versions allow, and an older one writes nothing.

Screenshots

The picker on the first launch after an update, from a release-profile build. Before is main, which says nothing.

	Light	Dark
Before
After

What's New opens the About dialog, and its What's New row the release notes:

Light	Dark

Test plan

• application::tests::a_launch_after_a_newer_release_says_nothing_and_keeps_its_version: fails on the PR's first version.
• application::launch_notice::tests::only_a_launch_after_an_older_release_is_an_update: semver order, pre-releases, downgrades, an unreadable stored version.
• application::tests::the_first_launch_after_an_older_release_says_so_once, a_first_launch_records_the_version_and_says_nothing.
• about_dialog::tests::the_newest_release_has_notes_for_whats_new.
• ui::session_window::launch_notice::tests: What's New opens the About dialog and the notice stays read, an update and a crash on each page, a second notice replaces only its own kind, the crash notice.
• tablepro-storage settings::last_seen_version_starts_empty_and_round_trips.
• tablepro 2543 passed, tablepro-storage 223 passed, lint clean.
• WhatsNewContentTests: olderBuildIsQuiet fails on main; stableAfterBetaShowsLinkOnce, legacyVersionRecordCarriesOver. notesShowLinkForNewVersion (now notesShowLinkForNewerBuild) and firstLaunchHasNoLink pinned the old version key and now check the build key. 15 passed with PreferenceKeysGuardTests.
• FirstRunPlanTests.olderVersionShowsNothing and OnboardingPreferencesTests.olderVersionKeepsNewerRecorded fail on main; numeric order tests beside them.
• A release-profile build under Xvfb: an older stored version shows the toast and records the new one; a newer stored version shows nothing and stays.

[datlechin]

looks great