Skip to content

🤖 fix: bump Go to 1.26.10 and go-jose to v4.1.6 - #393

Merged
ThomasK33 merged 1 commit into
mainfrom
go-1.26.10-go-jose-4.1.6
Oct 29, 2026
Merged

ThomasK33 merged 1 commit into
mainfrom
go-1.26.10-go-jose-4.1.6

Conversation

@ThomasK33

Copy link
Copy Markdown
Member

Summary

Bumps the Go toolchain from 1.26.9 to 1.26.10 and github.com/go-jose/go-jose/v4 from v4.1.4 to v4.1.6. This clears the new findings that make every merge-queue run fail since the vulnerability database updates after 2026-10-15.

Background

The merge-group run of #391 (run 40940296865) failed three checks on findings in main's dependencies:

  • lint: govulncheck reports GO-2026-6809 in crypto/x509@go1.26.9, which the code reaches from servingcert.Bundle.NeedsRenewal (internal/aggregated/servingcert/servingcert.go:277). Go 1.26.10 fixes it.
  • Trivy filesystem scan and Trivy image scan: CVE-2026-116587 (HIGH) in go-jose v4.1.4, an indirect dependency. v4.1.6 fixes it.

main last ran CI green on 2026-10-15, so main itself fails these checks now, and no PR can pass the queue until this lands. This follows the pattern of #222.

Implementation

  • go.mod: go 1.26.10, go-jose v4.1.6 (go get, go mod tidy, go mod vendor). No other module moved.
  • AGENTS.md, CONTRIBUTING.md, README.md: the Go version mentions.

Validation

With Go 1.26.10:

  • GOFLAGS=-mod=vendor go tool govulncheck ./... reports no called vulnerabilities.
  • Trivy v0.74.0 (the CI version): trivy fs --skip-dirs vendor --severity HIGH,CRITICAL on the tree, and trivy rootfs on a CGO_ENABLED=0 build of the binary. Both report 0 findings.

Risks

Low. This is a toolchain patch release plus a patch bump of an indirect dependency. The GoReleaser release path was not dry-run locally. It reads the Go version from go.mod through setup-go, as before.


Generated with mux • Model: anthropic:claude-opus-5-5 • Thinking: high • Cost: $17.93

Clears GO-2026-6809 (crypto/x509, reached from servingcert.Bundle.NeedsRenewal),
which fails govulncheck in the required lint job, and CVE-2026-116587
(go-jose v4.1.4), which fails the Trivy filesystem and image scans.

_Generated with `mux` • Model: `anthropic:claude-opus-5-5` • Thinking: `high`_

Change-Id: Id95ac0e64470190ff76d2cde9e06d702ebfa9622
Signed-off-by: Thomas Kosiewski <tk@coder.com>
@ThomasK33

Copy link
Copy Markdown
Member Author

@codex security review

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 29, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-29T19:58:53.345530Z bd1dd2c PR opened
🔒 Security Review ✅ Completed 2026-10-29T20:00:17.307064Z bd1dd2c Manual request
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector

Copy link
Copy Markdown

🛡️ Codex Security Review

Security review completed. No security issues were found in this pull request.

Reviewed commit: bd1dd2c23f

View security finding report

Only the user who started this review can view the report in Codex.

ℹ️ About Codex security reviews in GitHub

This is an experimental Codex feature. Security reviews are triggered when:

  • You comment "@codex security review"
  • A regular code review gets triggered (for example, "@codex review" or when a PR is opened), and you’re opted in so security review runs alongside code review

Once complete, Codex will leave suggestions, or a comment if no findings are found.

@ThomasK33
ThomasK33 added this pull request to the merge queue Oct 29, 2026
@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Oct 29, 2026
@ThomasK33
ThomasK33 added this pull request to the merge queue Oct 29, 2026
Merged via the queue into main with commit 458b480 Oct 29, 2026
9 of 10 checks passed
@ThomasK33
ThomasK33 deleted the go-1.26.10-go-jose-4.1.6 branch October 29, 2026 21:14
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