{{ message }}
Repository navigation
🌱 Bump Scorecard to the v5.6.0 candidate and fix the canary toolchain - #1714
Merged
justaugustus merged 2 commits intoOct 11, 2026
Merged
Conversation
setup-go exports GOTOOLCHAIN=local through $GITHUB_ENV, which overrode the job-level GOTOOLCHAIN=auto. The first run failed resolving Scorecard main, which needs Go 1.26.5, on the Go 1.25.7 setup-go installed from go.mod, before building or testing anything. Set GOTOOLCHAIN=auto through $GITHUB_ENV after setup-go so later steps can follow Scorecard's go.mod floor. Assisted-by: LLM Signed-off-by: Stephen Augustus <foo@auggie.dev>
Move github.com/ossf/scorecard/v5 to 61e84743, the commit planned for the v5.6.0 tag, ahead of the v2.5.0 release. This lets the dependency updates it brings in replace several open Dependabot PRs now, and the pin moves to the v5.6.0 tag once it exists. The go directive moves from 1.25.7 to 1.26.5, Scorecard's minimum. Assisted-by: LLM Signed-off-by: Stephen Augustus <foo@auggie.dev>
justaugustus
marked this pull request as ready for review
October 11, 2026 20:19
This was referenced Oct 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Two commits:
1. Fix the canary's Go toolchain handling. The first canary run (38170501940) failed before building anything:
actions/setup-goexportsGOTOOLCHAIN=localthrough$GITHUB_ENV, which overrode the job-levelGOTOOLCHAIN: auto, sogo get github.com/ossf/scorecard/v5@maincouldn't move from the Go 1.25.7 ingo.modto the 1.26.5 Scorecard now needs. The job now writesGOTOOLCHAIN=autoto$GITHUB_ENVaftersetup-go, so later steps follow Scorecard'sgo.modfloor. Without this, the canary would fail the same way every time Scorecard raises its Go version, instead of testing the change.2. Bump Scorecard to the v5.6.0 release candidate (
61e84743,v5.5.1-0.20261011173757-61e847433562). The pin moves to thev5.6.0tag once it exists (#1710). Thegodirective moves from 1.25.7 to 1.26.5, Scorecard's minimum; the Docker builder (golang:1.26.5) already meets it.The bump's dependency updates supersede these Dependabot PRs: #1693 (go-git, now v5.19.3), #1699 (buildkit, now v0.32.2), #1701 (grpc, now v1.83.2), #1704 (x/net, now v0.60.0), #1706 (otel/sdk, now v1.45.0), and #1708 (containerd, no longer in the module graph). #1695 (cosign v2.6.5) is not covered.
Verification, locally on this branch:
go mod verify,go build ./...andgo test ./...(withGITHUB_AUTH_TOKEN) pass;zizmorreports no findings forcanary.yml. Aworkflow_dispatchcanary run after merge confirms the toolchain fix.Tracking: #1710