Repository navigation
ci: build two release targets at a time - #200
Conversation
goreleaser runs as many tasks at once as GOMAXPROCS, so the runner built four targets in parallel. On 2026-10-27 the release-snapshot job of #199 was killed three times during that build step, with a runner shutdown signal and exit code 137. The last success was on 2026-10-26. Pass --parallelism=2 to goreleaser in the release-snapshot job and in the release workflow, so both build two targets at a time. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Zsolt Gaspar <17578237+zsltg@users.noreply.github.com>
|
No actionable comments were generated in the recent review.
 |
| Layer / File(s) | Summary |
|---|---|
Set parallel build limit .github/workflows/ci.yml, .github/workflows/release.yml |
Both GoReleaser commands now use --parallelism=2. The CI workflow comments note that four concurrent builds previously ended with exit 137. |
Priority:
Estimated code review effort: 1 (Trivial) | ~5 minutes
Change: Bug fix
Suggested reviewers: codescene-access
Merge Risk: 
8b979
-
The release workflows are consistently configured and ready for normal validation.
Pre-merge checks: 
-
Check name Status Explanation Title check The title clearly and concisely describes the main change: limiting GoReleaser to two concurrent release targets. Description check The description includes the required What and why and Checks sections. It explains the failure context, the proposed fix, and the status or rationale for each listed check. Docstring Coverage No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat… Linked Issues check Check skipped because no linked issues were found for this pull request. Out of Scope Changes check Check skipped because no linked issues were found for this pull request. Full details: Docstring Coverage
-
Explanation
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (2 skipped: 2 unsupported.)
-
Finishing Touches
-
🧪 Generate unit tests (beta)
-
- Commit to this branch
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
Comment @coderabbitai help to get the list of available commands.
![codescene-access[bot]](https://avatars.githubusercontent.com/in/3755875?s=60&v=4){kind=small}
|
@coderabbitai review Generated by Claude Code |
✅ Action performed
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #200 +/- ##
=======================================
Coverage 96.43% 96.43%
=======================================
Files 145 145
Lines 14563 14563
=======================================
Hits 14044 14044
Misses 518 518
Partials 1 1 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
What and why
On 2026-10-27 the
release-snapshotjob of #199 was killed three times, at the same step. goreleaser was building the five targets, and the runner stopped the job with a shutdown signal (exit code 137 once, 143 twice). The job runs only when a release input changes. Its last success was on 2026-10-26.goreleaser runs as many tasks at once as
GOMAXPROCS, so the 4-core runner built four targets in parallel. This PR passes--parallelism=2in therelease-snapshotjob and inrelease.yml, so both build two targets at a time. The real release would otherwise probably fail the same way.This PR changes no release input, so its own CI does not run
release-snapshot. That is the documented design: the comment in thechangesjob says the next pull request that changes a release input tests an edit to these steps. #199 changesgo.mod, so it will be the proof after this merges.Checks
make check(actionlint and zizmor included)make cover: not needed, no Go code changesmake security: left to CIscripts/mutation-gate.sh: not needed, no Go code changesrelease-snapshotrun of fix(deps): bump the rdb fork to stop a print to stdout #199 after this mergesscripts/capabilities.sh: not needed,go.modandgo.sumdid not changeGenerated by Claude Code
Summary by CodeRabbit