Add guarded Apple release workflows - #638
Merged
Merged
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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
Adds reusable GitHub Actions building blocks for Apple releases so app repositories can keep their release wiring small and repeatable.
The workflows verify immutable source and shared-tool commit SHAs, share one repository-wide Apple release lock, clean up temporary App Store Connect keys, and can resume a version branch after an interrupted PR-creation step.
Review and public release remain explicit actions. Nothing in this change merges a version PR, submits a build for review, or releases an approved version automatically.
Consumer shape
An app repository pins one published PowerForge version and checksum in
.powerforge/powerforge.tool.json, then calls the reusable version, advance, or approval workflow at an exact commit SHA.Validation
net472buildactionlintacross all reusable workflows