Repository navigation
chore: prepare v0.2.0 release - #52
Merged
Merged
Conversation
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.
What
Bump PhoneCam to v0.2.0 so a later
v0.2.0tag (no-rc) becomes the GitHub Latest release andgo install …@latestinstalls this CLI instead of v0.1.0.version0.2.0-rc.1→0.2.0versionName0.2.0-rc.1→0.2.0,versionCode2 → 3 (so the APK upgrades over rc.1)@latesttester block; Status is v0.2.0 with Arch+vivo and Fedora+Motorola+OBSNo media, pairing, or workflow changes.
.github/workflows/release.ymlalready publishes a non-prerelease when the tag has no-rc/-beta/-alpha.Why
v0.2 planned work is on
main. Two real setups work. The rc is blocking@latestand keeping v0.1.0 as GitHub Latest.Tests
Notes
This PR does not tag or attach binaries. After merge: tag
v0.2.0, wait for the CLI release workflow, then attach the signed APK (same keystore as v0.1.0 / rc.1).