Repository navigation
Add trusted Android attestation and publishing workflows - #27
Merged
Merged
Conversation
This was referenced Oct 16, 2026
kruton
changed the title
kruton
force-pushed
the
trusted-android-workflows
branch
from
October 16, 2026 15:51
4f626a5 to
48fc115
Compare
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.
Application builds stay in the source repository, alongside Java/SDK setup, Gradle tasks, flavor matrices, output paths, and release metadata. Add isolated reusable workflows for unsigned-artifact attestation, final Android verification/attestation, and GitHub Releases / Play alpha publishing.
android-attest.ymlaccepts only a profile label and attests a stable artifact handoff from its own GitHub run/attempt without checking out or executing application code. Finalizer and publisher jobs load public signing policy from protectedconnectbot/.githubby immutable source repository ID. The VM authorizes the protected reusable-workflow identity, so routine caller edits do not require policy hash updates.Only version 3 policies with explicit trusted builder and finalizer identities are supported. Remove content-pin authorization, caller-local policy defaults, and the same-repository finalizer fallback.
Validation: 46 shared-action tests and workflow linting pass. Both signing profiles completed in the earlier live flow; finalization encountered a release-asset digest mismatch, so full end-to-end verification remains a production gate. Companion changes: connectbot/connectbot#2527, connectbot/.github#9, and runtime branch update #29.