Add CI checks and store candidate builds - #1
Merged
Conversation
Run analysis, tests, and Android and iOS release builds on pull requests and manual branch runs without using release credentials. Use rc tags to build signed candidates with configuration and signing credentials from Infisical, then upload them to Play internal testing and TestFlight. Check in dependency lockfiles and the Gradle wrapper, and document the maintainer setup and candidate release process.
Resolve hosted runner image drift by locating sdkmanager through the Android SDK root and installing CocoaPods from a checksummed Bundler lockfile.
Update Flutter plugin podspec checksums for the locked Ruby and CocoaPods toolchain so deployment-mode installs match clean runners.
Pin Google Play uploads to the Anycast package and internal testing track so runtime configuration cannot redirect a release.\n\nEncode temporary Android signing values before loading them as Java properties, and exercise escape sequences in the CI signing password.
sljeff
commented
Jul 29, 2026
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
1 participant
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 changed
mainrc-*candidates to Play internal testing and TestFlightStore uploads only run for a tag that exactly matches the version in
pubspec.yamland points to a commit onmain. After testing, the sameAAB and IPA can be promoted without rebuilding them. GitHub does not keep
the build artifacts.
Testing
bash -n scripts/*.shshellcheck -x scripts/*.shactionlint .github/workflows/*.ymlflutter pub get --enforce-lockfileflutter analyze --no-fatal-infosflutter testNo builds were uploaded to either store during testing. Creating the first
matching
rc-*tag after merge will start the real uploads.