Update Node.js version to 18.x in release workflow

[himorishige]

リリース用のCIがNode16になっていたので、Node18環境へ変更しました

Summary by CodeRabbit

• Chores
  • Updated GitHub Actions workflow to use the latest versions for better performance and compatibility.

[coderabbitai]

Walkthrough

The update to .github/workflows/release.yml enhances the GitHub Actions workflow by upgrading the actions used for checking out the repository and setting up Node.js. Specifically, it moves to the latest major versions of these actions and shifts the Node.js version used in the workflow to the more recent '18.x', ensuring compatibility with newer features and improvements in performance and security.

Changes

File	Change Summary
.github/workflows/...	Updated checkout and setup-node actions to v4; Node.js version changed to '18.x'

Poem

In the land of code and byte,
A rabbit hopped with great delight.
🌟 "To v4 we leap, with Node in tow,
🚀 Through the web's vast, endless row.
With each upgrade, we aim to be,
Swift and secure, as you can see!"
🐰💻 So cheers to changes, big and small,
Together, we hop towards progress for all.

---

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 95aee51 and 9db5165.

Files selected for processing (1)

• .github/workflows/release.yml (1 hunks)

Additional comments: 2

.github/workflows/release.yml (2)

• 12-13: The updates to the checkout and setup-node actions to version 4 are appropriate and follow best practices for maintaining up-to-date dependencies in CI workflows.
• 15-15: Updating the Node.js version to '18.x' is a positive change, ensuring the CI process uses a more current and supported version of Node.js. This aligns with best practices for software maintenance and security.