chore: align release command with ios conventions#841
Merged
Conversation
- Use release-{version} branch naming (e.g. release-2.1.0)
- Fix stale master by adding git pull after checkout
- Use --notes-file to avoid shell expansion in release notes
Made-with: Cursor
This comment has been minimized.
This comment has been minimized.
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
Made-with: Cursor
ovitrif
approved these changes
Mar 13, 2026
Collaborator
ovitrif
left a comment
ovitrif
left a comment
There was a problem hiding this comment.
lgtm 👏🏻
Thank you for iterating on this and bringing consistency in the question 🥇
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.
This PR aligns the Android
/releasecommand with the conventions established in the iOS release automation (bitkit-ios#478).Description
release-{version}branch naming (e.g.release-2.1.0) instead ofrelease/{versionCode}git pullwhen branching from master (skip for tags)--notes-filewith a temp file for prepending store release notes, avoiding shell expansion issues with backticks and$in PR titlesPreview
N/A
QA Notes
N/A — changes only affect the
/releaseautomation command, no app code modified.Made with Cursor