Skip to content

chore: prepare v0.2.0 release - #52

Merged
kvm404 merged 1 commit into
mainfrom
chore/release-v0.2.0
Aug 31, 2026
Merged

kvm404 merged 1 commit into
mainfrom
chore/release-v0.2.0

Conversation

@kvm404

@kvm404 kvm404 commented Aug 31, 2026

Copy link
Copy Markdown
Owner

What

Bump PhoneCam to v0.2.0 so a later v0.2.0 tag (no -rc) becomes the GitHub Latest release and go install …@latest installs this CLI instead of v0.1.0.

  • CLI version 0.2.0-rc.1 → 0.2.0
  • Android versionName 0.2.0-rc.1 → 0.2.0, versionCode 2 → 3 (so the APK upgrades over rc.1)
  • README: drop the pin-to-rc.1 / do-not-use-@latest tester block; Status is v0.2.0 with Arch+vivo and Fedora+Motorola+OBS

No media, pairing, or workflow changes. .github/workflows/release.yml already 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 @latest and keeping v0.1.0 as GitHub Latest.

Tests

cd linux-cli && go test ./... && go test -race ./...
JAVA_HOME=/usr/lib/jvm/java-17-openjdk cd android && ./gradlew testDebugUnitTest

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).

@kvm404
kvm404 merged commit e95e7c2 into main Aug 31, 2026
2 checks passed
@kvm404
kvm404 deleted the chore/release-v0.2.0 branch August 31, 2026 06:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant