Skip to content

fix(ci): bump Go to 1.26.10 for GO-2026-6809 - #114

Open
cristim wants to merge 1 commit into
mainfrom
fix/go-1-26-10
Open

cristim wants to merge 1 commit into
mainfrom
fix/go-1-26-10

Conversation

@cristim

@cristim cristim commented Oct 21, 2026 •

Copy link
Copy Markdown
Member

Bumps the pinned Go version from 1.26.9 to 1.26.10 (go.mod/go.work, docs) and adds a CHANGELOG entry.

Why: govulncheck fails CI with GO-2026-6809 (crypto/x509, found in go1.26.9, fixed in go1.26.10), blocking every PR.

Verification (go1.26.10): go build and go test -count=1 ./... pass in every module; govulncheck@v1.1.4 ./... reports no vulnerabilities in code per module.

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Documentation

    • Updated installation and contribution prerequisites to require Go 1.26.10.
    • Documented the Go upgrade addressing a security issue in crypto/x509.
  • Maintenance

    • Updated the project’s Go language version to 1.26.10.

Pin Go 1.26.10 in go.mod/go.work, workflow defaults and docs so govulncheck
no longer reports the crypto/x509 vulnerability fixed in 1.26.10.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Oct 21, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration
  • Configuration used: Repository: LeanerCloud/cloud-commitments-mcp/.coderabbit.yaml
  • Review profile: CHILL
  • Plan: Essentials
  • Run ID: e15288a9-f776-4f5d-8d87-039c875dda1a
📥 Commits

Reviewing files that changed from the base of the PR and between d49fb20 and 2ff4d7d.

⛔ Files ignored due to path filters: 1
  • go.work is excluded by !**/*.work
📒 Files selected for processing: 4
  • CHANGELOG.md
  • CONTRIBUTING.md
  • README.md
  • go.mod

Included review availability: This review used your included allowance. 0 included reviews remain after this review. Your included PR review attempts over the past 7 days set your current allowance at 1 review per hour.

📝 Walkthrough

The module requirement and Go version documentation changed from 1.26.9 to 1.26.10. The changelog records the update for GO-2026-6809 in crypto/x509.

Changes: Go Version Update

Layer / File(s) Summary
Go version requirement and documentation
go.mod, CONTRIBUTING.md, README.md, CHANGELOG.md
The module requirement and setup documentation now specify Go 1.26.10. The changelog records the upgrade for GO-2026-6809 in crypto/x509.

Priority: ➖ Normal

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Bug fix

Merge Risk: ⚪ Minimal · up to 2ff4d

The version and documentation updates are consistent and mergeable.

Pre-merge checks: Passed 5
Check name Status Explanation
Description Check Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check Passed The title clearly and concisely describes the main change: updating Go to 1.26.10 to address GO-2026-6809.
Docstring Coverage Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (4 skipped: 4 unsupported.)

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Comment @coderabbitai help to get the list of available commands.

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