add Go 1.22 to the build matrix

[shogo82148]

Summary by CodeRabbit

• Chores
  • Updated Go versions in CI workflow to include "stable" and "1.22" alongside existing versions.

[coderabbitai]

Walkthrough

The recent update focuses on enhancing the GitHub Actions workflow by broadening the Go versions tested against. Specifically, it introduces "stable" and "1.22" to the mix, ensuring compatibility with the latest stable release and extending support to a wider range of versions, including "1.21" and "1.20".

Changes

Files	Summary
.github/.../test.yml	Updated Go versions in the matrix: added "stable" and "1.22" to the test suite.

🐇✨
In the realm of code, where the bits do leap,
A change was made, not shallow, but deep.
"Stable" and "1.22", now join the fray,
Ensuring our builds, will no longer stray.
So here's to the code, may it run swift and true,
A toast from the burrow, we bid you adieu! 🚀🥕
🐇✨

---

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>.
  • Generate unit-tests 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 tests 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 show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 4c41ec1 and 36c7e14.

Files selected for processing (1)

• .github/workflows/test.yml (3 hunks)

Additional comments: 3

.github/workflows/test.yml (3)

• 18-19: The addition of Go versions "stable" and "1.22" to the Linux job's build matrix is a good practice for ensuring compatibility with the latest Go releases.
• 49-50: The inclusion of "stable" and "1.22" in the macOS job's build matrix aligns with the goal of maintaining up-to-date compatibility with Go versions.
• 80-81: Adding "stable" and "1.22" to the MinGW job's Go version matrix is a prudent step for ensuring the project's cross-platform compatibility with the latest Go versions.