Write down what changed for users since 4.6 - #566
Merged
Conversation
The store listing has carried the same three release notes since 2024 - 137.txt, 93.txt and 82.txt all say "Fix potential crash while saving changes for a document" - so every release since has gone out with whatever the console last had, and there is nowhere in the tree that says what a user got. One file per release under fastlane/metadata, named by version code, which is what `fastlane supply` uploads as the Play Console release notes. The codes jump: 4.6, 4.7 and 4.8.0 were counted by hand (202-204) and everything from 4.9.0 on is derived from the tag (40900 and up). All of them are inside Play's 500 character limit. CHANGELOG.md is the same history at more length, for the repo and for github releases. Three of the eight releases say "maintenance release, no visible changes", because that is what they were: 4.6 was CI cleanup and a submodule bump of renovate commits, 4.8.0 was the release workflow and the instrumented test flakiness, and 4.12.0 was moving odrcore from a conan build to the maven central AAR. Core changes are folded into the release that absorbed them rather than listed on their own, since a user has no way to tell where a change came from. That puts almost everything in 4.7, which took odrcore 5.2.0 -> 5.7.1 in one go: the whole PDF renderer, the built-in doc/xls/ppt implementations, and the drop of the pdf2htmlEX and wvWare backends. Nothing about formats that disappeared and came back - the csv table viewer that died with the 6.2 upgrade and returned in #564 reads only as "text, images, archives and media are shown by the engine", and the lite review prompt that had been dead since 4.2 is not described as broken. Play-facing wording says "our own engine" rather than naming odrcore, which store readers have no reason to know. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01XZaMTmVQ1QTv3hHy4Kxt34
![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: 5646facc6e
ℹ️ About Codex in GitHub
Codex has been enabled to automatically 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 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The store listing has carried the same three release notes since 2024 -
137.txt,93.txtand82.txtall say "Fix potential crash while saving changes for a document" - so every release since has gone out with whatever the console last had, and there is nowhere in the tree that says what a user got.What is here
fastlane/metadata/android/en-US/changelogs/<versionCode>.txt- one file per release, which is whatfastlane supplyuploads as the Play Console release notes. The codes jump because the scheme changed under #538: 4.6, 4.7 and 4.8.0 were counted by hand, everything from 4.9.0 on is derived from the tag.202.txt203.txt204.txt40900.txt41000.txt41100.txt41200.txt41300.txtAll eight are inside Play's 500 character limit; the longest is 462.
CHANGELOG.md- the same history at more length, for the repo and for github releases.Judgement calls
Core changes are folded into the release that absorbed them, rather than listed on their own, since a user has no way to tell where a change came from. That puts almost everything in 4.7, which took odrcore 5.2.0 -> 5.7.1 in one go: the whole PDF renderer (fonts, images, vector graphics, transparency, encryption, links, CJK), the built-in doc/xls/ppt implementations, and the drop of the pdf2htmlEX and wvWare backends under #480.
Three releases say "maintenance release, no visible changes", because that is what they were - 4.6 was CI cleanup and a submodule bump of renovate commits, 4.8.0 was the release workflow and the instrumented test flakiness, and 4.12.0 was moving odrcore from a conan build to the maven central AAR (#558). Better than inventing something.
Nothing about formats that disappeared and came back. The csv table viewer that died with the 6.2 upgrade and returned in #564 reads only as "text, images, archives and media are shown by the engine", and the lite review prompt that had been dead since 4.2 (#559) is not described as having been broken - 4.13.0 just says the prompt appears less often.
Play-facing wording says "our own engine" rather than naming odrcore, which store readers have no reason to know.
CHANGELOG.mdsays "the built-in engine" for the same reason.Documentation only - no code, no build files, nothing that runs.
🤖 Generated with Claude Code