go-directive-bump-needs-ci-go-version
Use when raising the go directive in go.mod, or CI fails with 'go.mod requires go >= X (running go Y; GOTOOLCHAIN=local)'. Make CI install the go.mod version.
89%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Go directive bump needs CI to install that Go
Trigger: you raise go in go.mod, or CI fails with go.mod requires go >= 1.26.10 (running go 1.26.9; GOTOOLCHAIN=local).
Fix: let the workflow read the version from go.mod:
- uses: actions/setup-go@v6
with:
go-version-file: go.modWhy: actions/setup-go@v6 sets GOTOOLCHAIN=local, so Go cannot download the newer toolchain itself. A range such as go-version: 1.26.x without check-latest resolves to the runner's cached patch, which can be older than go.mod. Older setup-go versions keep GOTOOLCHAIN=auto, so the same bump passes in one workflow and fails in another.
- Repository
coralogix/terraform-provider-coralogix
- Revision
75b5730
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.