ci: Upgrade Go & other

[klauspost]

Summary by CodeRabbit

• New Features

  • Upgraded to Go version 1.23.x, enhancing performance and introducing new features.
  • Updated GoReleaser to version 2.3.2, optimizing the release process.

• Bug Fixes

  • Adjusted Go version in the project module for improved compatibility and functionality.

[coderabbitai]

Walkthrough

The pull request includes updates to the Go version specifications in the CI/CD workflows and the Go module file. The .github/workflows/go.yml and .github/workflows/release.yml files have been modified to reflect the new Go versions 1.21.x, 1.22.x, and 1.23.x, replacing older versions. Additionally, the Go module version in go.mod has been updated from 1.20 to 1.21. These changes ensure alignment with the latest Go features and improvements.

Changes

Files	Change Summary
.github/workflows/go.yml	Updated Go version matrix from [1.20.x, 1.21.x, 1.22.x] to [1.21.x, 1.22.x, 1.23.x]. Updated setup steps to use 1.23.x.
.github/workflows/release.yml	Upgraded Go version from 1.22.x to 1.23.x and GoReleaser version from 1.24.x to 2.3.2.
go.mod	Changed Go version declaration from go 1.20 to go 1.21.

Sequence Diagram(s)

sequenceDiagram
    participant CI as CI/CD Workflow
    participant Go as Go Environment
    participant GoReleaser as GoReleaser Tool
    participant Module as Go Module

    CI->>Go: Set up environment with Go 1.23.x
    CI->>GoReleaser: Execute release command
    GoReleaser->>Module: Build and package module
    Module-->>GoReleaser: Return built artifacts
    GoReleaser-->>CI: Complete release process

Loading

Poem

🐰 In fields of code, we hop and play,
With Go versions bright, we leap today!
From one to twenty-three, we cheer,
New features bloom, let’s spread the cheer!
With every change, our project grows,
A rabbit's joy in every code that flows! 🌼

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 26519f8 and 304537c.

Files selected for processing (3)

• .github/workflows/go.yml (5 hunks)
• .github/workflows/release.yml (1 hunks)
• go.mod (1 hunks)

Files skipped from review due to trivial changes (1)

• go.mod

Additional comments not posted (7)

.github/workflows/release.yml (2)

24-24: LGTM!

Upgrading to Go 1.23.x is a good move to leverage the latest performance improvements, features, and bug fixes while maintaining backward compatibility.

---

29-29: Verify compatibility with GoReleaser v2.

Upgrading to GoReleaser v2.3.2 and pinning to a specific version is a good practice to ensure a predictable and reproducible release process.

However, as this is a major version upgrade, please verify that the existing GoReleaser configuration is compatible with the new version and make any necessary adjustments.

.github/workflows/go.yml (5)

15-15: LGTM!

Updating the go-version matrix to include the latest three minor versions of Go is a good practice to ensure compatibility. Removing 1.20.x suggests that the project no longer supports that version.

---

57-57: LGTM!

Updating the go-version to 1.23.x in the setup step ensures consistency with the latest version specified in the matrix.

---

79-79: LGTM!

Updating the go-version to 1.23.x in the setup step ensures consistency with the latest version specified in the matrix.

---

119-119: LGTM!

Updating the go-version to 1.23.x in the setup step ensures consistency with the latest version specified in the matrix.

---

190-190: LGTM!

Updating the go-version to 1.23.x in the setup step ensures consistency with the latest version specified in the matrix.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  -- I pushed a fix in commit <commit_id>, please review it.
  -- Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  -- @coderabbitai generate unit testing code for this file.
  -- @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  -- @coderabbitai generate interesting stats about this repository and render them as a table.
  -- @coderabbitai read src/utils.ts and generate unit testing code.
  -- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  -- @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[wwqgtxx]

Can you consider maintaining the minimum golang version in go.mod as 1.20?

I compared v1.17.10 and v1.17.9 and found that they did not use any 1.21 language features.

Golang 1.21 has abandoned support for many older operating system versions (such as windows7, 8/server2008, 2012).

Rolling back to 1.20 allows downstream projects to update to the latest klauspost/compress without giving up support for existing platforms.

This may increase the maintenance cost of this project, but there is no need to pay extra costs when no 1.21 feature code is included.

[klauspost]

@wwqgtxx My policy is to support one more version than the stdlib does.

You are welcome to do a "light fork", or pin your dependency at existing versions, but the world moves on.