Skip to content

CI: always use the newest Go patch release - #6

Merged
Vayz0001 merged 1 commit into
mainfrom
go-1274
Nov 11, 2026
Merged

Vayz0001 merged 1 commit into
mainfrom
go-1274

Conversation

@Vayz0001

Copy link
Copy Markdown
Member

setup-go reused the runner's cached Go 1.27.3, so govulncheck on main flagged GO-2026-6859 (net/http, fixed in Go 1.27.4).

Adds check-latest: true to every setup-go step (tests, vulncheck, release, ollama-compat), so CI and release builds always get Go security patches.

🤖 Generated with Claude Code

setup-go reused the runner's cached Go 1.27.3, so govulncheck flagged
GO-2026-6859 (net/http, fixed in Go 1.27.4). check-latest makes every
job, including release builds, pick up Go security patches.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Vayz0001
Vayz0001 merged commit f8b0669 into main Nov 11, 2026
15 checks passed
@Vayz0001
Vayz0001 deleted the go-1274 branch November 11, 2026 03:54
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