Repository navigation
Add gated CI and opt-in internal TestFlight releases - #22
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.
Chime has a manual TestFlight release path but no repository CI. This draft adds checks for relevant PR changes and an explicitly disabled-by-default internal TestFlight job for validated, app-changing main commits. It is independent of the dot bridge in #21 and includes no app-client changes.
Behavior
internal-testflightenvironment, serializes uploads, and rechecks current main before archive and upload.contents: readGitHub permission.(offset + run_number).run_attempt.0across all three targets; retry attempts get distinct builds. Xcode build-number management is disabled during export.testFlightInternalTestingOnly=trueprevents external TestFlight/App Store distribution. No gateway deployment, tester invitations or App Store submission.Activation stays a separate operator decision
The release job cannot run until
TESTFLIGHT_UPLOAD_ENABLED=trueis explicitly set and the protected environment, branch restrictions/reviewers, build offset and Apple environment secrets are configured. Missing configuration fails closed. No credentials, environment permissions, live uploads, provisioning changes or deployments were created/performed in this task.See setup, security boundaries and operations. The workflow uses GitHub's official Xcode 27 preview image, pinned to the Xcode 27.0 app path; image availability remains an external dependency. Preserve the documented build-number namespace when mixing manual and CI releases.
Validation
Hosted CI run 37006320923 passed on final commit
eb6308dca0e74fd6f9ac09a95a93499c39e61a5e: pipeline tests/lint, gateway tests, iPhone/Watch checks and the validation gate are green. Internal TestFlight was skipped as intended.git diff --checkpassed.npm run typecheckand 67 unit tests passed on clean main-based code.scripts/check-watch.sh, iPhone simulator build, Watch simulator build, unsigned Release archive all passed; archive verifies iPhone + embedded Watch + widgets with matching versions.1012.2.0build override with signing disabled.