ci: upload each release to App Store Connect - #120
Merged
Merged
Conversation
Adds an app-store job that archives the AppStore configuration unsigned, then lets xcodebuild -exportArchive sign it with the team's cloud-managed Apple Distribution certificate (authenticated with an Admin App Store Connect API key) and upload it. It runs alongside the Developer ID build and isn't a dependency of the GitHub release, so an upload failure can't block a release. Submitting for review stays manual.
|
🎉 This PR is included in version 2.28.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
Summary
Adds an
app-storejob to the release workflow. On each release it:AppStoreconfiguration without a real signaturexcodebuild -exportArchivewith cloud signing, which signs the app with the team's cloud-managed Apple Distribution certificate and uploads it to App Store ConnectIt authenticates with an Admin App Store Connect API key (
ASC_API_KEY_P8,ASC_API_KEY_ID,ASC_API_ISSUER_ID) and stops immediately, naming the secret, if any of the three is missing.The job runs alongside the Developer ID
buildjob, andreleasedoesn't depend on it, so a failed upload can't block a GitHub release. Creating the App Store version and submitting for review stay manual.As a
ci:commit, this won't trigger a release.