john-okeefe/Anitrack
1
0
Fork 1
Code Issues Pull Requests Actions Packages Projects Releases 30 Wiki Activity

docs: summarize v3 migration and note stale v2 key entries

Browse Source 
Add docs/V3_MIGRATION.md — a full write-up of the wailsv3 desktop migration (backend/frontend/build/CI changes, verification, branch map) and the planned follow-ups (toolchain majors + Android sideload). No behavior change.

Add a short notice to README.md: Migrating from v2 — v2 and v3 Secret Service collections coexist (AniTrack vs login) so both versions keep working after the first v3 re-login; the orphaned v2 entries are harmless. Details in docs/V3_MIGRATION.md. No cleanup instructions, by request.
This commit is contained in:
John O'Keefe
2026-09-13 17:52:53 -04:00
parent 2ab0843a0c
commit 2b4eb31495
2 changed files with 53 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+4
View File
@@ -36,6 +36,10 @@ Please follow the instructions [here](https://v3.wails.io/getting-started/your-f
To run in live development mode, run `make dev` in the project directory (it runs `wails3 dev`). This starts a Vite development
server on http://localhost:5173 with very fast hot reload of your frontend changes, alongside the desktop app window.
## Migrating from v2
The `wailsv3` branch moves AniTrack from Wails `v2` → `v3` and from `99designs/keyring` → `zalando/go-keyring`. Both versions can coexist: on Linux, `v2` tokens live in an `AniTrack` Secret Service collection while `v3` uses the `login` collection, so one does not overwrite the other. After you log into AniList / MAL / Simkl once on `v3`, the `v2` entries become stale but harmless orphans — leave them if you still run both versions, or clear the old collection when you’ve fully moved over. See `docs/V3_MIGRATION.md` for the full migration summary and next steps (including planned Android support).
## Building
To build a redistributable, production mode package, use `make build`. The binary lands at `build/bin/AniTrack`.