chore: upgrade go version to 1.23

[flc1125]

Summary by CodeRabbit

• Chores
  • Updated the Go language settings across automation and dependency configurations to require Go 1.23 and above, including adjustments to testing parameters.
• Documentation
  • Revised the public-facing version badge to reflect the new Go version support, ensuring users see the current minimum requirement.

[coderabbitai]

Warning

Rate limit exceeded

@dosubot[bot] has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 26 minutes and 49 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between f90a902 and 6ac88e7.

📒 Files selected for processing (5)

• .github/workflows/lint.yml (1 hunks)
• .github/workflows/test.yml (1 hunks)
• README.md (1 hunks)
• go.mod (1 hunks)
• renovate.json (1 hunks)

Walkthrough

The pull request updates the Go language version used across the project’s configuration. It modifies GitHub Actions workflows to use a specific version (1.23.x) instead of the dynamic 'stable' tag and revises the test matrix by removing Go 1.22.x. Additionally, the README badge, Go module declaration, and renovate configuration have been updated to require Go version 1.23. These changes ensure consistency in the project's development and CI/CD processes.

Changes

File(s)	Summary of Changes
.github/workflows/lint.yml, .github/workflows/test.yml	Updated Go version settings: lint workflow now uses 1.23.x instead of stable; test matrix revised to remove 1.22.x (retaining 1.23.x and 1.24.x).
README.md, go.mod, renovate.json	Updated minimum Go version from 1.22.10 to 1.23: documentation badge, module declaration, and renovate version constraint adjusted accordingly.

Possibly related PRs

• build(go): upgrade Go version to 1.22.10 #34: The changes in the main PR, which update the Go version to 1.23.x, are related to the retrieved PR that previously upgraded the Go version to 1.22.10, as both involve modifications to the Go version in the workflow files.
• support go 1.24 #45: The changes in the main PR are related to the updates in the Go version specified in the GitHub Actions workflow, which aligns with the modifications made in the retrieved PR regarding the Go version matrix in the test workflow.
• build(go.mod): update module go version to 1.21 #23: The changes in the main PR, which update the Go version to 1.23, are related to the retrieved PR that updates the Go version to 1.21, as both involve modifications to the go.mod file and reflect changes in the Go version used for the project.

Suggested labels

size:M

Poem

I'm a rabbit with a coder's delight,
Hopping through configs in the late night.
From "stable" to "1.23.x" the changes do gleam,
Each updated line is part of my dream.
I nibble on code like a crunchy, sweet treat—
Celebrating progress with every heartbeat!

---

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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @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 generate docstrings to generate docstrings for this PR. (Beta)
• @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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 94.40%. Comparing base (f90a902) to head (6ac88e7).
Report is 1 commits behind head on v2.x.

Additional details and impacted files

@@           Coverage Diff           @@
##             v2.x      #48   +/-   ##
=======================================
  Coverage   94.40%   94.40%           
=======================================
  Files           1        1           
  Lines         304      304           
=======================================
  Hits          287      287           
  Misses         15       15           
  Partials        2        2           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.