ci: raise release build-binaries timeout to 60 minutes - #6743
Merged
Conversation
aarch64-apple-darwin hit the previous 30-minute limit and was cancelled on the v0.22.4 release run. Direct consequence of removing sccache from this job: a cold --features full build (including the heavier candle/ML dependencies) now compiles from scratch on every release instead of reusing a warm cache.
github-actions
Bot
added
documentation
bug-ops
enabled auto-merge (squash)
August 16, 2026 17:19
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
build-binariesjob timeout from 30 to 60 minutes inrelease.ymlaarch64-apple-darwinhit the previous 30-minute limit and was cancelled on the v0.22.4 release run (#31959609206). Direct consequence of removing sccache in #6742: a cold--features fullbuild (including the heavier candle/ML dependencies) now compiles from scratch on every release instead of reusing a warm cache.Test plan
gitleaks protect --staged