fix(ci): pin security audit to Go 1.25.11 to clear crypto/tls govulncheck findings#144
Merged
Merged
Conversation
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
1 participant
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.
Problem
The scheduled Security Audit workflow's Go Dependency Audit job fails because
go-version: "1.25"resolves to an earlier patch than 1.25.11, andgovulncheckflagscrypto/tlscall chains that are fixed in 1.25.11.Fix
Pin
go-version: "1.25.11"in.github/workflows/security.ymlto match thetoolchain go1.25.11directive inbackend/go.mod. This ensures govulncheck runs against the exact same toolchain version used in production and CI builds.Test plan