Skip to content

fix: update Go version to 1.26 and dependencies for security improvements#55

Open
t4niwa wants to merge 3 commits into
masterfrom
fix/x-net-vulnerability
Open

fix: update Go version to 1.26 and dependencies for security improvements#55
t4niwa wants to merge 3 commits into
masterfrom
fix/x-net-vulnerability

Conversation

@t4niwa
Copy link
Copy Markdown

@t4niwa t4niwa commented Jun 4, 2026

Description

Bump golang.org/x/net from v0.23.0 to v0.55.0 to fix a known vulnerability.

Since the newer x/net needs a recent toolchain, I also bumped Go 1.23 to 1.26.

While at it I fixed a go vet warning in third_party/webhook/authz.go.

No behavior change.

Nothing in garm itself changed functionally. go build and go test -race ./... pass.

Assignees

  • Assignees is set

Type of changes

  • dependencies
  • bug (go vet fix)

Flags

  • Breaks backward compatibility
  • Requires a documentation update
  • Has untestable code

Checklist

  • Followed the guidelines in the CONTRIBUTING document
  • Added prefix [skip ci]/[ci skip]/[no ci]/[skip actions]/[actions skip] in the PR title if necessary
  • Tested and linted the code
  • Commented the code
  • Made corresponding changes to the documentation

Checklist for maintainer

  • Use Squash and merge
  • Double-confirm the merge message has prefix ...
  • Delete the branch after merge

…ents

Signed-off-by: taniwa <taniwa@lycorp.co.jp>
@t4niwa t4niwa self-assigned this Jun 5, 2026
@t4niwa t4niwa requested a review from fsul7o June 5, 2026 08:40
Comment thread go.mod Outdated
t4niwa added 2 commits June 5, 2026 18:04
…ents

Signed-off-by: taniwa <taniwa@lycorp.co.jp>
Signed-off-by: taniwa <taniwa@lycorp.co.jp>
@fsul7o fsul7o changed the title fix: update Go version to 1.25 and dependencies for security improvements fix: update Go version to 1.26 and dependencies for security improvements Jun 5, 2026
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.

2 participants