ci: bump release upload-assets timeout to 60 minutes#463
Conversation
Windows builds (cargo, no LLD) consistently land 25-28 minutes against the previous 30-minute cap, leaving no headroom for runner variance. Bump all targets to 60 min for a uniform, comfortable ceiling. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Greptile SummaryThis PR increases the Confidence Score: 5/5Safe to merge — single-line CI config change with clear empirical justification and no functional risk. No logic, security, or correctness issues. The new 60-minute limit is a sensible upper bound that still protects against truly stuck jobs while giving Windows runners adequate headroom. No files require special attention. Important Files Changed
Reviews (1): Last reviewed commit: "ci: bump release upload-assets timeout t..." | Re-trigger Greptile |
Benchmark changesVersions:
Public ratios: warm installs vs Bun 6x -> 8x; warm installs vs pnpm 10x -> 13x.
daf6cbd vs ba7f671 | aube/bun/pnpm | 3 scenarios | 3 runs | 500mbit/50ms | generated by Codex. |
Summary
Windows release builds consistently land 25-28 min against the 30-min cap (v1.6.0: 25m43s / 27m11s; v1.6.1 just timed out at 30m on aarch64-pc-windows-msvc). Bump every upload-assets target to 60 min so runner variance doesn't tip releases over.
Test plan
release.ymlfor v1.6.1 withtag: v1.6.1after merge → confirm Windows tarballs land🤖 Generated with Claude Code
Note
Low Risk
Low risk: CI-only change that just allows more time for release build/upload jobs; no product code or security logic is modified.
Overview
Increases the GitHub Actions
release.ymlupload-assetsjob timeout from 30 to 60 minutes to reduce release failures from long/variable build times (notably on Windows).Reviewed by Cursor Bugbot for commit daf6cbd. Bugbot is set up for automated code reviews on this repo. Configure here.