Repository navigation
docs: complete signed release pipeline - #29
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.
Summary
Validation
The signed-release pipeline has now been exercised successfully on
mainusing the protected GitHub
releaseenvironment and the real release signingmaterial.
Successful workflow run:
Validated commit:
The workflow successfully:
The resulting GitHub Actions artifact is:
Previous failure and fix
The first production run exposed an
apksigneroutput-format differencebetween the local Android Build Tools version and the GitHub-hosted runner.
PR #28 made the certificate parser compatible with both formats while keeping
the single-signer and certificate-fingerprint protections intact.
The corrected workflow then completed successfully on
main.Roadmap
Completes:
The next Phase 5 item is: