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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Build failure:
go build ./...fails on this PR because GitHub Actions resolves.go-version(1.26) to1.26.3— theactions/go-versionsmanifest hasn't published1.26.4yet. WithGOTOOLCHAIN=local(the default in CI), Go refuses to build a module requiring a newer version than the installed toolchain:Two paths forward:
actions/go-versionspublishes1.26.4, then re-run CI. This is the simplest option and the change itself is correct.toolchaindirective togo.mod(e.g.toolchain go1.26.4) so that Go's toolchain auto-download kicks in even when the runner ships an older patch. This decouples the module requirement from the CI runner's cached version. Note: this requiresGOTOOLCHAINto not be set tolocalin CI.The go.mod change itself is sound — it's purely a CI timing issue.