Repository navigation
Ask for the Android release note with the change that needs it - #452
Merged
Merged
Conversation
The note in `apps/android/store/whatsnew/` is uploaded with every Play build, but nothing an agent reads said to update it, so a change could ship under the previous version's "What's new". The guidance lived only in `apps/android/store/README.md`, which an agent has no reason to open. The "Shipping to Play" section now says a change someone would notice on their phone updates the note in the same pull request, how it accumulates until `versionName` changes, and what leaves it alone. PushThat adopted the same rule when it took over this publish flow. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
CI uploads
apps/android/store/whatsnew/whatsnew-en-USas each Play build's "What's new", but nothing in AGENTS.md told an agent to update it. The guidance lived only inapps/android/store/README.md, so a change could ship under the previous version's note.This adds a paragraph to the "Shipping to Play" section:
versionNamelast changed, and starts over when the version is bumped (which is what the 0.2.0 and 0.2.1 notes did).PushThat just adopted the same publish flow and the same rule (MakeRocketGoNow/pushthat#12).
Docs only: no code changes.
🤖 Generated with Claude Code