Skip to content

ci: use the newest Go 1.26 patch for the backend - #16

Merged
Sulaiman-Dauda merged 1 commit into
mainfrom
ci-go-1.26-latest
Oct 21, 2026
Merged

Sulaiman-Dauda merged 1 commit into
mainfrom
ci-go-1.26-latest

Conversation

@Sulaiman-Dauda

Copy link
Copy Markdown
Owner

The backend job fails on every run since GO-2026-6809 was published. The Go range '>=1.25.12' let setup-go keep the runner's cached Go 1.26.9, and the crypto/x509 fix is in 1.26.10.

This asks for 1.26.x with check-latest, so CI fetches the newest 1.26 patch each run and later standard library fixes arrive without another edit. Locally govulncheck reports GO-2026-6809 on 1.26.9 and nothing on 1.26.10.

🤖 Generated with Claude Code

The range '>=1.25.12' let setup-go keep the runner's cached Go 1.26.9,
which carries GO-2026-6809 in crypto/x509, so govulncheck failed every
backend run. Asking for 1.26.x with check-latest fetches 1.26.10 now and
each later patch as Go ships it.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
@Sulaiman-Dauda
Sulaiman-Dauda merged commit 27afd4c into main Oct 21, 2026
2 checks passed
@Sulaiman-Dauda
Sulaiman-Dauda deleted the ci-go-1.26-latest branch October 21, 2026 08:05
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.

1 participant