Repository navigation
ci(release): give the tag's app job 180 minutes - #3539
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
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.
Why
The
appjob inrelease.ymlstops at 120 minutes. The same unsigned universal archive took 106 to 123 minutes in 5 of the last 23 Release Build runs onxcode-27, and the tag adds the CloudKit check, signing, export, two notarizations and packaging. The first tag could time out after holding a macOS runner for two hours.Change
appjob's limit is 180 minutes.Verified
actionlintpasses. Release Build step times come from runs 39117792525, 39142189647 and the 21 others since 2026-10-17.