Repository navigation
Signed release workflow, and update links that point at Ariane - #11
Merged
Merged
Conversation
Pushing a tag like v1.0.0 builds release APKs signed with a key kept in repository secrets and publishes them as a GitHub release. The version comes from the tag. Release builds get their own app ID (com.limelight.ariane) so they install next to Artemis, and the in-app update links now go to Ariane's releases. CI also builds the release variant so release-only build problems show up before tagging. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018kfakDid61ekVJbVztFn2H
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.
Before: there were no releases, release builds used Artemis's app ID, and the in-app "Software Update" links went to Artemis's releases.
After: pushing a tag like
v1.0.0publishes signed Ariane APKs on the Releases page. The app installs ascom.limelight.ariane, next to Artemis, and its update links point at this repository.How:
.github/workflows/release.ymlruns onv*tags:assembleNonRoot_gameReleasewith the version taken from the tag (1.2.3 → versionCode 10203).apksignerand checks that the passthrough encoder is included.gh release create.build.gradle, the release signing config readsARIANE_KEYSTORE*environment variables. Without them, release builds stay unsigned as before. Version name and code can be set with-P.🤖 Generated with Claude Code
https://claude.ai/code/session_018kfakDid61ekVJbVztFn2H
Generated by Claude Code