fix broken build on macos-latest

[shogo82148]

Summary by CodeRabbit

• Chores
  • Updated OS versions for testing in CI/CD pipeline.
  • Updated Go versions for testing in CI/CD pipeline.
  • Updated @types/node devDependency to the latest version.

[coderabbitai]

Warning

Rate limit exceeded

@shogo82148 has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 4 minutes and 50 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

Files that changed from the base of the PR and between 07c8e38 and da5fd82.

Walkthrough

The recent updates primarily focus on enhancing the compatibility of the CI/CD pipeline and aligning dependencies with current standards. Specifically, OS versions for testing have been diversified, adding specific versions for Ubuntu, macOS, and Windows. The Go language version scheme was modified, and the @types/node devDependency in package.json was updated to a newer version.

Changes

File	Change Summary
.github/.../test.yml	Updated OS versions for testing (specific Ubuntu, macOS, and Windows versions). Adjusted the Go versions for testing.
package.json	Updated the devDependency @types/node from ^16.18.3 to ^20.14.8.

Poem

A rabbit hops in code delight,
Switching versions in the night,
From Ubuntu's past to future bright,
And macOS gleaming in new light,
Windows too, joins this flight,
Our code now tests with all its might.
Dependencies cozy, tucked in tight. 🐇

---

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 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 show all the console.log statements in this repository.
  • @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 as 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.

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.
• 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.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 008e2ef and 07c8e38.

Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

Files selected for processing (2)

• .github/workflows/test.yml (1 hunks)
• package.json (1 hunks)

Additional comments not posted (3)

package.json (1)

30-30: Verify compatibility of updated @types/node version.

The update of @types/node from "^16.18.3" to "^20.14.8" jumps several major versions. It's crucial to ensure that this update does not introduce any compatibility issues with other dependencies or the project's Node.js version.

.github/workflows/test.yml (2)

51-58: Approval of OS version specifications.

Specifying exact OS versions (ubuntu-24.04, ubuntu-20.04, ubuntu-18.04, macos-14, macos-13, macos-12, windows-2022, windows-2019) is a good practice to avoid issues related to automatic updates in *-latest versions. Consider adding a comment in the workflow file explaining the reason for these specific versions to maintain clarity for future maintainers.

---

57-58: Verify the oldstable Go version.

The update from Go version "1.11" to "oldstable" is noted. It's important to verify what specific version "oldstable" refers to at the moment, to ensure it aligns with the project's compatibility and stability requirements.