Skip to content

ci: build with Go 1.27.3 (GO-2026-6809) - #115

Merged
FumingPower3925 merged 1 commit into
mainfrom
ci/go-1.27.3-toolchain
Oct 21, 2026
Merged

FumingPower3925 merged 1 commit into
mainfrom
ci/go-1.27.3-toolchain

Conversation

@FumingPower3925

Copy link
Copy Markdown
Contributor

Refs the v1.6.0 release run (no issue closed by this PR). Sibling of goceleris/celeris#1102.

The govulncheck step of the CI vulncheck job fails on main since the vulnerability database update: GO-2026-6809 (crypto/x509), corrected in go1.27.3, reachable on the root module through h1client.go:309 -> tls.Conn.Write (exit 3 with go1.27.2). This moves the toolchain from 1.27.2 to 1.27.3.

Changed (version strings only, 9 files):

  • go directive in the root go.mod, internal/integrationtest/testserver/go.mod and .github/tools/go.mod
  • every go-version in .github/workflows (ci, codspeed, coverage, release; 8 occurrences)
  • the "Go 1.27.2 or newer" statements in README.md and CONTRIBUTING.md

Not changed: go.sum files (go mod tidy leaves the tree identical in all three modules). No code change, so RULE 74 is not engaged.

Verified in golang:1.27.3 linux/arm64 (Docker, lane-local caches), with the repo's own CI invocations:

  • go build ./... && go vet ./... clean on the root and the testserver module
  • go test -race -count=1 -timeout 300s ./... ok (root 115.9 s, checkpoint)
  • govulncheck ./... (v1.8.0, the pinned scanner) on the root module and on internal/integrationtest/testserver: "No vulnerabilities found", exit 0 (root exited 3 with go1.27.2)
  • go tool -modfile=.github/tools/go.mod actionlint: clean (v1.7.12)

OWED: nothing beyond the CI run on this PR (the macOS and CodSpeed jobs only exist there).

@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: goceleris/loadgen/.coderabbit.yaml
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 3d8eb3d9-60bd-42c2-9cd2-a7676a9b8a73
📥 Commits

Reviewing files that changed from the base of the PR and between 15dc0a2 and b1fc357.

📒 Files selected for processing: 9
  • .github/tools/go.mod
  • .github/workflows/ci.yml
  • .github/workflows/codspeed.yml
  • .github/workflows/coverage.yml
  • .github/workflows/release.yml
  • CONTRIBUTING.md
  • README.md
  • go.mod
  • internal/integrationtest/testserver/go.mod
🔗 Linked repositories identified

CodeRabbit considers these linked repositories for cross-repo context during reviews:

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

📜 Recent review details
⏰ Context from checks skipped due to timeout: 1
  • GitHub Check: Benchmarks (CodSpeed walltime, arm64 macro runner)
🧰 Additional context used
📚 Code guidelines: 1
CONTRIBUTING.md — configured
📓 Path-based instructions: 4
A nested module that pins its own celeris and is spawned as a subprocess by the integration tests.

⚙️ CodeRabbit configuration file

Files:

  • internal/integrationtest/testserver/go.mod
Every uses: is pinned to a full commit SHA with a version comment (the repository requires SHA pinning).

⚙️ CodeRabbit configuration file

Files:

  • .github/workflows/coverage.yml
  • .github/workflows/codspeed.yml
  • .github/workflows/release.yml
  • .github/workflows/ci.yml
README cluster-bench contract: Pass unless the PR adds, removes, renames or changes the JSON tag or meaning of a field of loadgen.Result or of a type nested in it (results.go and the types it references), or adds, removes or renames a flag...

📄 CodeRabbit inference engine (Custom checks)

Files:

  • README.md
Source excerpt: Fill in the pull request template (Summary, Changes, Test Plan, `Closes #…`).

📄 CodeRabbit inference engine (CONTRIBUTING.md)

Files:

  • README.md
🧠 Learnings: 1
📓 Common learnings
Learnt from: CR
Repo: goceleris/loadgen

Timestamp: 2026-10-21T02:36:36.560Z
Learning: Source excerpt:
# Contributing to loadgen

## Pull request flow

2. Keep each PR focused on a single change and include tests — a
   correctness fix without a regression test is not complete.
🔇 Additional comments: 9
.github/tools/go.mod: 1

8-8: LGTM!

go.mod: 1

3-3: LGTM!

internal/integrationtest/testserver/go.mod: 1

3-3: LGTM!

CONTRIBUTING.md: 1

11-11: LGTM!

README.md: 1

52-52: LGTM!

.github/workflows/ci.yml: 1

22-22: LGTM!

Also applies to: 51-51, 74-74, 93-93

.github/workflows/codspeed.yml: 1

85-85: LGTM!

.github/workflows/coverage.yml: 1

38-38: LGTM!

.github/workflows/release.yml: 1

74-74: LGTM!

Also applies to: 144-144

📝 Summary

Summary by CodeRabbit

  • Chores

    • Updated the project’s required Go version to 1.27.3.
    • Updated development, testing, benchmarking, coverage, and release workflows to use Go 1.27.3.
  • Documentation

    • Updated installation and contribution guidance to reflect Go 1.27.3.

The Go version changes from 1.27.2 to 1.27.3 across module requirements, workflow setup, and documentation.

Changes: Go version update

Layer / File(s) Summary
Module requirements and prerequisites
.github/tools/go.mod, go.mod, internal/integrationtest/testserver/go.mod, CONTRIBUTING.md, README.md
The module requirements now specify Go 1.27.3. Contributor and installation instructions now require Go 1.27.3 or newer.
Workflow Go setup
.github/workflows/ci.yml, .github/workflows/codspeed.yml, .github/workflows/coverage.yml, .github/workflows/release.yml
The CI, benchmark, coverage, and release workflows now configure Go 1.27.3.

Priority: ➖ Normal

Estimated code review effort: 2 (Simple) | ~5 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to b1fc3

The update aligns the project’s Go requirements, CI environments, and documentation with no identified merge-blocking risk.

Pre-merge checks: Passed 5
Check name Status Explanation
Title check Passed The title uses the required conventional-commit format with the valid type ci: and accurately describes the Go 1.27.3 toolchain update.
Description check Passed The description directly explains the Go toolchain update, the addressed vulnerability, the affected files, and the validation performed.
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.
Readme Cluster-Bench Contract Passed PASS: The PR changes only Go version strings. results.go and cmd/loadgen/main.go are byte-identical between the base and head revisions, so no Result field, nested JSON schema, flag, or flag defau…
Full details: Readme Cluster-Bench Contract

Explanation

PASS: The PR changes only Go version strings. results.go and cmd/loadgen/main.go are byte-identical between the base and head revisions, so no Result field, nested JSON schema, flag, or flag default changed. The README change is only the Go 1.27.2 to 1.27.3 prerequisite update; the cluster-bench contract table remains unchanged.

✨ 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

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

@codecov

codecov Bot commented Oct 21, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@FumingPower3925
FumingPower3925 marked this pull request as ready for review October 21, 2026 02:36
@FumingPower3925
FumingPower3925 merged commit 6b8441e into main Oct 21, 2026
11 of 13 checks passed
@FumingPower3925
FumingPower3925 deleted the ci/go-1.27.3-toolchain branch October 21, 2026 03:45
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