Repository navigation
214 ships as 2.1.4 and its notes cover the salvage and the scan ghosts - #48
Conversation
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: eba80afb2b
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| Fixed: the reported import bug. Nested folders and multi-disc sets now scan correctly, sync failures are shown instead of hidden, and reconnecting after a network drop just works. | ||
|
|
||
| Also fixed: moving or deleting a book folder no longer leaves a ghost copy on your shelf. Downloaded books keep their track details through a library refresh, your sign-in stays bound to the server you typed, and switching between local files and your server no longer confuses where you left off. |
There was a problem hiding this comment.
When this What's New section is pasted into Google Play, the added paragraph increases the release notes from 487 to 786 characters, exceeding Play's 500-character per-language limit, so the Console will reject the intended 2.1.4 notes. Shorten the complete 2.1.4 section to 500 characters or fewer.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Fixed in e44c1bb. The v2.1.4 section is now 498 characters.
| versionCode = 213 | ||
| versionName = "2.1.3" | ||
| versionCode = 214 | ||
| versionName = "2.1.4" |
There was a problem hiding this comment.
With BuildConfig.VERSION_NAME now set to 2.1.4, users who last viewed 2.1.3 receive the New badge, but ChangelogData.releases still starts with a release labeled 2.1.3 and contains none of the newly advertised fixes. Opening that stale history then makes ChangelogViewModel record 2.1.4 as seen and removes the badge, so the app never presents an actual 2.1.4 entry; update the changelog data and its expected-version test alongside this bump.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Fixed in e44c1bb. 2.1.3 never reached users (213 was never uploaded), so the changelog's current entry is relabeled 2.1.4 and gains the three new fixes rather than adding a 2.1.4 entry above a 2.1.3 nobody had. ChangelogDataTest's expected list updated.
The What's New section is 498 characters, under the 500 Play allows per language. 2.1.3 never reached users, so the in-app changelog's current entry becomes 2.1.4 and carries the three new fixes instead of adding a second entry nobody upgraded past. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
1 participant
What
versionCode 213 to 214, versionName 2.1.3 to 2.1.4. The What's New in store-listing.md gains one paragraph in plain words for what landed since the 2.1.3 notes were written: the scan ghost fix (#45), downloaded track metadata surviving a refresh (#39), the auth token bound to its server (#37), and the mode-switch reliability work (#38, #44).
Last night's 213 bundle predates all of that, so 214 is the one that goes to the internal track.
Verification
assembleDebug and lintDebug clean on this head. bundleRelease built with the release signing config, manifest names 2.1.4.
Evidence: /home/static/nine-lives-evidence/2026-09-10-release-214/SUMMARY.md (bundle copy and sha256 beside it).
🤖 Generated with Claude Code