You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
docs: state the Go 1.26.10 minimum that go.mod requires - #58
README.md and examples/hello-eipc/README.md said "Go 1.22+" and CONTRIBUTING.md's prerequisites table said "1.21+", but go.mod requires go 1.26.10. All three now state 1.26.10 and point at the go line in go.mod.
Type of Change
feat — New feature
fix — Bug fix
docs — Documentation only
style — Formatting, no code change
refactor — Code restructuring without behavior change
test — Add or fix tests
build — Build system or dependency changes
ci — CI/CD pipeline changes
perf — Performance improvement
Changes
README.md:49: Go 1.22+ -> Go 1.26.10 or newer (the go line in go.mod sets this minimum).
examples/hello-eipc/README.md:7: the same line. The example builds from the root module, so it has the same minimum.
CONTRIBUTING.md:9: the prerequisites table cell 1.21+ -> 1.26.10+ (the go line in go.mod).
CONTRIBUTING.md:122 (chore: bump go version to 1.22) is an example commit message, not a requirement, and is left alone.
To find every place that names a Go version, including table cells:
On master 70748b2 this prints exactly the three lines above. On this branch it prints nothing.
Testing
Unit tests pass (ctest --test-dir build --output-on-failure)
Integration tests pass
Manual testing performed
New tests added for new functionality
Run on macOS 26 arm64 at 3353732. Go 1.22.12 and 1.26.10 were fetched with the Go toolchain mechanism (GOTOOLCHAIN=go1.x.y go version) and then run with GOTOOLCHAIN=local, so each one really is the version it reports.
Check
Command
Result
Go 1.22.12 (old stated minimum) on master 70748b2
GOTOOLCHAIN=local go build ./...
FAIL as expected: go: go.mod requires go >= 1.26.10 (running go 1.22.12; GOTOOLCHAIN=local)
Go 1.26.10 (new stated minimum) on this branch
GOTOOLCHAIN=local go build ./...
PASS
Docs vs go.mod, master
docs-check.sh <tree> (reads the go line, runs the grep above over every non-Go file, fails on any match that is not 1.26.10)
FAIL as expected: README.md:49, CONTRIBUTING.md:9, examples/hello-eipc/README.md:7
Docs vs go.mod, this branch
same
PASS: every match states Go 1.26.10
Build / vet (as in CI)
go build ./..., go vet ./...
PASS
Gofmt (as in CI)
gofmt -l cmd core transport
PASS, 0 files
Test (as in CI)
go test -race -count=1 ./...
PASS: 18 packages ok, 7 with no test files
Book build
book-build.yml
NOT RUN locally (needs pandoc/LaTeX; runs on this PR)
Pre-Submission Checklist
Code compiles without warnings (-Wall -Wextra -Werror for C): no code touched
All existing tests pass
New tests added for new functionality: docs only
Documentation updated if API changed: this is the documentation change
Go 1.22.12 against master, Go 1.26.10 against this branch, and the docs check before and after:
Additional Notes
The README gives the floor rather than a single version on purpose, so it stays right when a newer Go is used. If the floor in go.mod moves again, this line moves with it.
Summary by Sourcery
Documentation:
Update the README, contributor guide, and example documentation to consistently state Go 1.26.10 as the minimum supported version and reference go.mod.
Summary by CodeRabbit
Documentation
Updated the Go prerequisite across the project and example documentation to Go 1.26.10 or newer, replacing the previously stated minimum versions. This clarifies the version needed to work with the project.
README.md and examples/hello-eipc/README.md said Go 1.22+, and the
prerequisites table in CONTRIBUTING.md said 1.21+, but go.mod requires
go 1.26.10. The floor was raised to 1.26.9 for the October security
releases (48d4a4a) and then to 1.26.10 to distrust the compromised CA
keys (2315c1f, #49). A Go 1.22 toolchain with GOTOOLCHAIN=local stops
with "go.mod requires go >= 1.26.10".
Update the Go minimum in the project README and example README to match the requirement in go.mod.
README.md L49
examples/hello-eipc/README.md L7
Correct the Go version in the contributor prerequisites table to match the go.mod minimum.
CONTRIBUTING.md L9
Tips and commands
Interacting with Sourcery
Trigger a new review: Comment @sourcery-ai review on the pull request.
Continue discussions: Reply directly to Sourcery's review comments.
Generate a GitHub issue from a review comment: Ask Sourcery to create an
issue from a review comment by replying to it. You can also reply to a
review comment with @sourcery-ai issue to create an issue from it.
Generate a pull request title: Write @sourcery-ai anywhere in the pull
request title to generate a title at any time. You can also comment @sourcery-ai title on the pull request to (re-)generate the title at any time.
Generate a pull request summary: Write @sourcery-ai summary anywhere in
the pull request body to generate a PR summary at any time exactly where you
want it. You can also comment @sourcery-ai summary on the pull request to
(re-)generate the summary at any time.
Generate reviewer's guide: Comment @sourcery-ai guide on the pull
request to (re-)generate the reviewer's guide at any time.
Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
pull request to resolve all Sourcery comments. Useful if you've already
addressed all the comments and don't want to see them anymore.
Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
request to dismiss all existing Sourcery reviews. Especially useful if you
want to start fresh with a new review - don't forget to comment @sourcery-ai review to trigger a new review!
No actionable comments were generated in the recent review.
Walkthrough
Three documentation files now state that Go 1.26.10 is the minimum version. The README files refer to go.mod as the source of the minimum.
Changes: Go version requirement documentation
Layer / File(s)
Summary
Align documented Go requirements README.md, CONTRIBUTING.md, examples/hello-eipc/README.md
The three documents now state a minimum Go version of 1.26.10. The README files note that go.mod sets the minimum. CONTRIBUTING.md retains the stated purpose of building and testing EIPC.
The documentation now states the intended Go minimum; no merge-blocking risk is identified.
Pre-merge checks: 5
Check name
Status
Explanation
Description Check
Check skipped - CodeRabbit’s high-level summary is enabled.
Title check
The title clearly summarizes the main change: updating the documentation to state the Go 1.26.10 minimum required by go.mod.
Linked Issues check
Issue #57 requires the three documents to state the Go 1.26.10 minimum enforced by go.mod. The diff updates README.md, examples/hello-eipc/README.md, and the CONTRIBUTING.md prerequisites table to sta…
Out of Scope Changes check
The diff changes only the three Go-version documentation entries requested by issue #57. No unrelated changes are present.
Docstring Coverage
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Full details: Linked Issues check
Explanation
Issue #57 requires the three documents to state the Go 1.26.10 minimum enforced by go.mod. The diff updates README.md, examples/hello-eipc/README.md, and the CONTRIBUTING.md prerequisites table to state Go 1.26.10 or newer and reference the go line in go.mod.
Full details: Docstring Coverage
Explanation
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (3 skipped: 3 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
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.
File: No configuration file from this repository applied
Commit: Unavailable
Layers: defaults
Review profile: CHILL
Plan: Advanced
Run ID: b56d5036-d16c-4e5f-9219-09ecadf457e1
Commits
Reviewing files that changed from the base of the PR and between 70748b2 and 3353732.
Files selected for processing: 3
CONTRIBUTING.md
README.md
examples/hello-eipc/README.md
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.
• Correct the documented Go minimum from 1.21+/1.22+ to 1.26.10 across three guides.
• Point readers to the go line in go.mod as the source of the requirement.
Keep the explicit minimum in each prerequisite section and reference go.mod. A generated shared value would add machinery for three straightforward documentation statements.
Files changed (3) +3 / -3
Documentation (3) +3 / -3
CONTRIBUTING.mdCorrect the contributor Go prerequisite+1/-1
Correct the contributor Go prerequisite
• Changes the prerequisites table from Go 1.21+ to 1.26.10+ and identifies the 'go' line in 'go.mod' as its source.
Premise: pass — go.mod requires go 1.26.10; README.md:49 said Go 1.22+, CONTRIBUTING.md:9 said 1.21+, examples/hello-eipc/README.md:7 said Go 1.22+; all three now state 1.26.10 (docs-only, +3/-3).
Contract: n/a — docs-only.
CI: green @33537321 (16 checks; Build & Test all 3 OSes success; policy success).
Integration: Integration-unverified: infra (nightly Unified Build quota failure, 6th night).
Reviewer: loop run 2026-11-10 (stewardship batch 2, premise verified vs live master)
Second look: n/a (not multi-look class)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
Summary
README.mdandexamples/hello-eipc/README.mdsaid "Go 1.22+" andCONTRIBUTING.md's prerequisites table said "1.21+", butgo.modrequiresgo 1.26.10. All three now state 1.26.10 and point at thegoline ingo.mod.Type of Change
Changes
README.md:49:Go 1.22+->Go 1.26.10 or newer (the go line in go.mod sets this minimum).examples/hello-eipc/README.md:7: the same line. The example builds from the root module, so it has the same minimum.CONTRIBUTING.md:9: the prerequisites table cell1.21+->1.26.10+ (the go line in go.mod).CONTRIBUTING.md:122(chore: bump go version to 1.22) is an example commit message, not a requirement, and is left alone.To find every place that names a Go version, including table cells:
On master
70748b2this prints exactly the three lines above. On this branch it prints nothing.Testing
Run on macOS 26 arm64 at
3353732. Go 1.22.12 and 1.26.10 were fetched with the Go toolchain mechanism (GOTOOLCHAIN=go1.x.y go version) and then run withGOTOOLCHAIN=local, so each one really is the version it reports.70748b2GOTOOLCHAIN=local go build ./...go: go.mod requires go >= 1.26.10 (running go 1.22.12; GOTOOLCHAIN=local)GOTOOLCHAIN=local go build ./...go.mod, masterdocs-check.sh <tree>(reads thegoline, runs the grep above over every non-Go file, fails on any match that is not 1.26.10)README.md:49,CONTRIBUTING.md:9,examples/hello-eipc/README.md:7go.mod, this branchgo build ./...,go vet ./...gofmt -l cmd core transportgo test -race -count=1 ./...book-build.ymlPre-Submission Checklist
Closing issue
Fixes #57
Screenshots / Logs
Go 1.22.12 against master, Go 1.26.10 against this branch, and the docs check before and after:
Additional Notes
The README gives the floor rather than a single version on purpose, so it stays right when a newer Go is used. If the floor in
go.modmoves again, this line moves with it.Summary by Sourcery
Documentation:
Summary by CodeRabbit