Fix goreleaser parallel builds (use CLI flag, not config field) - #956
Conversation
GitHub-hosted runners are being killed mid-build when all 4 cross-compilation targets run concurrently. Pass --parallelism 2 to goreleaser to reduce peak resource usage without making the build fully sequential. Also reverts the invalid parallelism field from .goreleaser.yml.
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: openshift/coderabbit/.coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (3)
Cache: Disabled due to data retention organization setting Knowledge base: Disabled due to data retention organization setting WalkthroughThe release workflows now pass ChangesRelease parallelism
Estimated code review effort: 1 (Trivial) | ~2 minutes ✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
🧪 Generate unit tests (beta)
Comment |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dustman9000 The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
🤖 Finished Review · ✅ Success · Started 12:51 PM UTC · Completed 12:59 PM UTC Commit: Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $1.98 |
|
Review skipped — this PR is already merged. The Posted by fullsend pre-review check |
|
Review skipped — this PR is already merged. The Posted by fullsend post-review check |
Follow-up to #955. The
parallelismfield doesn't exist in goreleaser's build config schema -- it needs to be passed as a CLI flag instead. This caused the release to fail immediately with a YAML unmarshal error.Changes:
parallelism: 2from.goreleaser.yml--parallelism 2via the goreleaser actionargsin bothrelease.yamlandrelease-on-version-bump.yamlSummary by CodeRabbit