Skip to content

chore(go): require Go 1.27 - #103

Merged
barad1tos merged 2 commits into
mainfrom
chore/go-1-27
Sep 28, 2026
Merged

barad1tos merged 2 commits into
mainfrom
chore/go-1-27

Conversation

@barad1tos

@barad1tos barad1tos commented Sep 28, 2026 •

Copy link
Copy Markdown
Owner

── Summary ─────────────────────────────────

Require Go 1.27 consistently across the module, CI, CodeQL, and installation instructions. The existing module still declared Go 1.26.2 while the local upgrade used 1.27, which left CI and its linter on the older toolchain.

── Changes ─────────────────────────────────

  • Chore: Set the module minimum to Go 1.27 and run CI/CodeQL with Go 1.27.1; update golangci-lint to v2.14.0, which is built with Go 1.27.1.
  • Chore: Normalize go.mod and go.sum; the x/sync and x/sys version updates are already on main.
  • Refactor: Apply the Go 1.27 idioms identified by modernize in domain routing and daemon option literals without changing their values.
  • Docs: Update the Go requirement in README and the loop-scope test comment; align existing README tables with the editor's Markdown inspection.

── Validation ──────────────────────────────

  • go build ./... — passed.
  • go vet ./... — passed.
  • golangci-lint run ./... (v2.14.0) — 0 issues.
  • go mod tidy -diff — no changes.
  • go test -p=1 -count=1 -race -coverpkg=./... -covermode=atomic ./... — passed, 83.9% statement coverage.
  • Pre-commit hooks including zizmor, gofmt, vet, lint, tidy, and tests — passed.

── Notes ───────────────────────────────────

Go 1.27 is now the minimum supported version. The CI toolchain is pinned to the current 1.27.1 patch release.

Summary by Sourcery

Align the project’s module, tooling, CI, code, and documentation with Go 1.27.

Enhancements:

  • Adopt Go 1.27 language and API idioms while preserving existing behavior.

Build:

  • Require Go 1.27 for the module and normalize module metadata.

CI:

  • Run build and CodeQL workflows on Go 1.27.1 and upgrade golangci-lint to v2.14.0.

Documentation:

  • Update contributor and user documentation to state the Go 1.27 minimum and align README Markdown formatting.

@sourcery-ai

sourcery-ai Bot commented Sep 28, 2026 •

Copy link
Copy Markdown

Reviewer's Guide

The PR makes Go 1.27 the consistent minimum across module metadata, CI, CodeQL, linting, tests, and user documentation, while applying behavior-preserving Go idiom and composite-literal updates; validation reports clean builds, vet/lint/tidy checks, and race-enabled tests.

File-Level Changes

Change Details Files
Align the supported and executed Go toolchain at Go 1.27.
  • Raise the module directive to Go 1.27.
  • Pin build CI and CodeQL to Go 1.27.1.
  • Upgrade golangci-lint to v2.14.0 to match the newer toolchain.
  • Normalize module metadata and sums.
go.mod
go.sum
.github/workflows/build.yml
.github/workflows/codeql.yml
Adopt Go 1.27-compatible idioms while preserving behavior.
  • Replace SplitN-based prefix extraction with strings.Cut.
  • Flatten daemon option literals to match the current option structure.
  • Update affected test fixtures to construct daemon options consistently.
bear/domain/canonical.go
bear/domain/routing.go
cmd/noxctl/daemon.go
tests/bear/engine/daemon_test.go
Update documentation and comments for the new minimum Go version and Markdown formatting.
  • Change README runtime and installation requirements to Go 1.27+.
  • Update the loop-scope test comment to reference go.mod's Go version.
  • Normalize existing README table formatting and simplify image markup.
README.md
tests/bear/config/daemon_test.go

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!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 28, 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-09-28T20:05:37.887102Z dceec0a 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.

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've found 2 issues

Prompt for AI Agents
Please address the comments from this code review:

## Individual Comments

### Comment 1
<location path="go.mod" line_range="3" />
<code_context>
 module github.com/barad1tos/noxctl

-go 1.26.2
+go 1.27

 require (
</code_context>
<issue_to_address>
**nitpick:** The repository now requires Go 1.27, but CONTRIBUTING.md still instructs contributors to install Go 1.26 or newer, and tests/bear/config/dispatch_test.go still describes Go 1.26 in its comment. These references contradict the module's minimum and can lead contributors to use an unsupported toolchain.

**Suggested fix:** Update the remaining Go 1.26 references in CONTRIBUTING.md and tests/bear/config/dispatch_test.go to Go 1.27.
</issue_to_address>

### Comment 2
<location path="README.md" line_range="1" />
<code_context>
-<p align="center">
-  <img src="docs/screenshots/repo_facade.svg" alt="noxctl — declarative Bear notes for the terminal" width="100%" />
-</p>
+<img src="docs/screenshots/repo_facade.svg" alt="noxctl — declarative Bear notes for the terminal" width="100%" />
</code_context>
<issue_to_address>
**nitpick:** The README image is no longer wrapped in the previous centered `<p align="center">` element, so it renders with the Markdown document's default alignment instead of centered like the prior README.

**Suggested fix:** Retain the centering wrapper or replace it with an equivalent Markdown-supported alignment mechanism.

```suggestion
<p align="center">
  <img src="docs/screenshots/repo_facade.svg" alt="noxctl — declarative Bear notes for the terminal" width="100%" />
</p>
```
</issue_to_address>

Sourcery assessment

Approved.


Sourcery is free for open source - if you like our reviews please consider sharing them ✨

Comment thread go.mod
Comment thread README.md

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a65f14f54f

ℹ️ 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread go.mod
@codecov

codecov Bot commented Sep 28, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

Keep the module minimum, CI toolchains, and lint version aligned so dependency updates are checked with the compiler version this repository supports.

1. Toolchain: require Go 1.27, use Go 1.27.1 in CI and CodeQL, and pin golangci-lint 2.14.0.
2. Compatibility: apply the Go 1.27 struct literal and string idioms reported by the updated linter without changing runtime behavior.
3. Docs and checks: update the installation requirement, test comment, checksums, and README formatting.

Impact: local builds and CI consistently require Go 1.27 or newer.
@barad1tos

Copy link
Copy Markdown
Owner Author

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Already looking forward to the next diff.

Reviewed commit: dceec0ad1c

ℹ️ 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@barad1tos
barad1tos merged commit f9193a8 into main Sep 28, 2026
12 checks passed
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