changelog/v<major>/<major>.<minor>.x/<version>.md for each of the 42 releases from v1.0.0 to v4.7.1, and changelog/beta/ for pre-releases (none has been published; its README says how one would be filed). CHANGELOG.md becomes the index: what the layout is, [Unreleased] exactly as it was, and a table per major version (version, date, edition) that links each file. Each file is its section, copied byte for byte except that its heading is the file's H1 (so the sub-headings move up one level, outside code fences), relative links gain ../../../ so they name the same repository paths, and the --- separators between sections are gone. Checked by reversing all three changes on every file and comparing with the original section: 40 of 40 equal. Two releases had no section: v1.0.0 (its GitHub release notes, which the changelog pointed to as "Initial stable") and v1.1.3 (its tag message). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
5.4 KiB
5.4 KiB
v3.0.1 – 2026-05-07 (The "Desktop Actually Ships This Time" Edition)
Same-day post-v3.0.0 maintenance covering Phase 9 (auto-update foundations + CVE bumps + Device Flow scaffold), Phase 10 (Tauri build break + i18n full coverage + deps audit), and Phase 10.1 (minisign keypair rotation). The desktop release pipeline is now end-to-end green — desktop-v1.0.0 finally produces signed .msi / .exe / .dmg / .AppImage / .deb / .rpm artefacts with a valid latest.json for auto-update.
🖥️ Phase 9 — auto-update foundations (#56)
tauri-plugin-updaterwired intoweb/src-tauri/. Endpoint pinned to the Releases page so installed clients fetchlatest.jsonon launch.- Updater pubkey embedded in
tauri.conf.json(gated behind a no-op for mobile builds via#[cfg(not(any(target_os="android", target_os="ios")))]). - GitHub Device Flow scaffold added to Settings: signed-in users no longer have to paste a long-lived PAT — they kick off
https://github.com/login/device, type the user_code, and the app polls until token issuance. Falls back to PAT for the offline path. - Dependency CVE bumps (vite 5 → 7, vite-plugin-pwa 0.20 → 1.x). Path-traversal fix in source-map handling. No source changes required for the bumps.
- More i18n: a chunk of edit-drawer / activity / dashboard chrome got proper translation keys.
🛠️ Phase 10 — Tauri build break + full i18n + deps audit (#57)
- Tauri lib-name regression fixed. Phase 9's auto-updater work introduced a
f2p_tracker_lib::run()call inmain.rswithout declaring[lib]inCargo.toml. Cargo's implicit lib name isf2p_tracker(hyphens → underscores from the package name) so the call failed to resolve andcargo buildblew up. Added the explicit Tauri-2-template-style block:The triple crate-type keeps the door open for future[lib] name = "f2p_tracker_lib" crate-type = ["staticlib", "cdylib", "rlib"]tauri ios init/tauri android initwork thatlib.rs's#[cfg_attr(mobile, tauri::mobile_entry_point)]already implies. - i18n now reaches every chrome surface (~150 new keys across new namespaces
charts,activity,add,system,cmdk,about,bulk,detail,diff,dialogs,health). All 9 chart pages, Activity, Add, Health, Top Online, About headings, drawers (Edit / BulkEdit / Diff / GameDetail),PwaIndicator,QueryState,GpgQuickUnlock,Topbartooltips/aria-labels,Settingsrate-limit panel,BulkActionBarconfirm dialog,GamesTabletooltips, andCommandPaletteresolve throughuseTranslation. Long-form About prose stays English per thesettings.languageHintpolicy. Enum values (anti-cheat / genre / type_game / safe) stay dataset-stable. - Third-party deps audit. Walked
web/package.jsonagainstAbout → Stack & third-partyanddocs/ACKNOWLEDGEMENTs.md. Added missing entries:react-router-dom, the i18next stack (i18next+react-i18next+i18next-browser-languagedetector), Tauri 2 + plugins (shell / updater / process),echarts-for-react, the styling utilities (class-variance-authority/clsx/tailwind-merge/tailwindcss-animate), and PostCSS + autoprefixer. Vite version corrected 5 → 7 (was already bumped by Phase 9; About just hadn't caught up). ACKNOWLEDGEMENTs.mdrestructured into grouped sections (runtime/build, styling, UI primitives, routing & i18n, data & state, charts, crypto & PWA, desktop) with deep links + SPDX licences.web/src-tauri/Cargo.locknow committed for reproducible desktop builds.
🔑 Phase 10.1 — minisign keypair rotation (#58)
desktop-v1.0.0was failing at the final sign-updater-bundle step:minisign formats the error so the inner "Missing comment" is the symptom of a wrong password — when the password is wrong, decryption returns garbage and the expectedfailed to decode secret key: incorrect updater private key password: Missing comment in secret keyuntrusted comment: minisign encrypted secret keyheader bytes don't appear. The original keypair's password was lost, so the GH secret could no longer decrypt the key.- Re-keyed via
npx tauri signer generate --ci -p ""with no password. Stored at~/.tauri/f2p-tracker{,.pub}on the maintainer's box;web/src-tauri/.gitignoreextended (*.key,f2p-tracker{,.pub}) as a guardrail in case keys ever land insrc-tauri/during dev. - New pubkey baked into
tauri.conf.jsonplugins.updater.pubkey. GH secretsTAURI_SIGNING_PRIVATE_KEYandTAURI_SIGNING_PRIVATE_KEY_PASSWORDrotated viagh secret set(password = empty string). - Trade-off: any user already on a build signed with the old key would have their auto-update break. Nobody hit that path because Phase 9 / Phase 10 release runs both failed before publishing artefacts. Phase 10.1's rebuild is the first actually-shipped
desktop-v1.0.0.
🏷️ Tag handling
desktop-v1.0.0was force-pushed twice in this cycle as the workflow input commit advanced (Phase 9 → Phase 10 → Phase 10.1). The triggering tag is GPG-signed each time. Once the auto-update story is real users-on-it, future fixes should bumpdesktop-v1.0.xinstead of force-pushing.
📝 Docs (this release)
CHANGELOG.md— this entry.web/src-tauri/Cargo.toml+tauri.conf.json+.gitignore— Phase 10 / 10.1 changes documented in their own commit messages and PR bodies (#57, #58).