Skip to content

CodeRabbit review findings - #5

Merged
ErikBooijFR merged 2 commits into
masterfrom
chore/coderabbit-review
Aug 12, 2026
Merged

CodeRabbit review findings#5
ErikBooijFR merged 2 commits into
masterfrom
chore/coderabbit-review

Conversation

@ErikBooijFR

Copy link
Copy Markdown
Collaborator

When offering our fixes to the upstream repo (gmr#24), their automated CodeRabbit review came up with two more small issues. Fixed in that PR, carrying them over to our fork here.

ErikBooijFR and others added 2 commits August 12, 2026 10:44
README documents exit code 125 for invalid usage, and validateArgs
errors honor that, but a malformed flag never reaches the action:
cli.Command.Run returns the parse error to main, where log.Fatal
exits with status 1, breaking the documented contract. Set
OnUsageError to route parse errors through the same
cli.Exit(..., 125) path as other usage errors.

This also reports the error once, in the ERROR: prefix style, instead
of twice: previously cli printed "Incorrect Usage" plus a full help
dump and logrus then repeated the message.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The intent of requiring 1.26.5 (the crypto/tls fix for GO-2026-5856)
was expressed as go 1.26 plus a toolchain directive, but the toolchain
directive is only a suggestion: it is honored under the default
GOTOOLCHAIN=auto and silently ignored under GOTOOLCHAIN=local, where a
1.26.0 toolchain would build a binary without the fix. The go
directive is the mechanism that actually enforces a floor - an older
toolchain either auto-upgrades or fails loudly.

Raise the go directive to 1.26.5 and drop the now-redundant toolchain
line. The module is not importable as a library, so the stricter
directive burdens no dependents. CI stays on go-version: '1.26', which
setup-go resolves to the latest 1.26.x patch, so release builds keep
picking up future security fixes without manual bumps.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@ErikBooijFR
ErikBooijFR marked this pull request as ready for review August 12, 2026 08:47

@ankon ankon left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If this were my project I'd not do the readme thing (completely remove the go version). But it isn't, and this is likely what they will accept in the upstream PR, so: All good, ship it!

@ErikBooijFR
ErikBooijFR merged commit 49d323a into master Aug 12, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants