Repository navigation
Keep the GitHub release text and name the released APK cleanly - #113
Merged
Merged
Conversation
- The upload step (svenstaro/upload-release-action with a fixed body and overwrite) replaced whatever was written in the GitHub release with "This is my release text". It is now a short gh CLI script: a release written by hand keeps its title and text, and the English Play Store notes (whatsnew/whatsnew-en-US) are added below them - once, so a re-run doesn't repeat them. A tag pushed without a release gets one, titled with the tag, with the notes as its text. gh needs contents: write. - The signing step appends "-signed" to Gradle's "reversatile-release-<version>-unsigned.apk", which made "...-unsigned-signed.apk". The signed APK is renamed to "reversatile-<version>.apk" before it goes to Play and the release. Both scripts were run locally against a stand-in gh for an existing release with text, an empty one, a missing one and a second run. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01V5G4cWSLBkiNNK4KC3zvXM
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
2 participants
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.
Two things from the 2.0.0 release. Only
.github/workflows/release.ymlchanges.Release text was overwritten
svenstaro/upload-release-actionran withoverwrite: trueand a fixedbody. It replaced the text of the hand-written "Analyze" release with "This is my release text".That step is now a short
ghCLI script.ghis preinstalled on the runners, and the job getspermissions: contents: write.whatsnew/whatsnew-en-US) are appended below. They are only added once, so a re-run doesn't repeat them.git push): A release is created, titled with the tag, with the notes as its text.APK was named
...-unsigned-signed.apkGradle names the unsigned release APK
reversatile-release-<version>-unsigned.apk, and the signing action appends-signedto that. A new step renames the signed APK toreversatile-<version>.apkbefore it goes to Play and to the GitHub release.Verification
gh. Cases covered: an existing release with text, an existing empty one, a missing one, and a second run of each (no duplicate notes).🤖 Generated with Claude Code
https://claude.ai/code/session_01V5G4cWSLBkiNNK4KC3zvXM
Generated by Claude Code