chore(deps): update Node.js version from 23.1.0 to 23.6.0

[yamadashy]

related: #240

Checklist

• Run npm run test
• Run npm run lint

[bolt-new-by-stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request updates the Node.js version across multiple configuration files and Dockerfiles from version 23.1.0 to 23.6.0. The changes include updating the .node-version and .tool-versions files, and modifying the base images in both the client and server Dockerfiles to use node:23-alpine. In the server Dockerfile, an additional dependency (curl) was also added to the installation list.

Changes

File	Change Summary
.node-version	Updated Node.js version from 23.1.0 to 23.6.0
.tool-versions	Updated Node.js version from 23.1.0 to 23.6.0
website/client/Dockerfile	Base image changed from node:22-alpine to node:23-alpine
website/server/Dockerfile	- Base image changed from node:22-alpine to node:23-alpine - Added curl to dependency installation

Possibly related PRs

• chore(deps): update Node.js engine to >=18.20.0 #239: Updates package.json engines field to require Node.js >=18.20.0
• fix(deps): downgrade cli-spinners to 2.9.2 #277: Modifies Node.js version matrix in CI workflow

---

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 92.12%. Comparing base (0d8ec45) to head (5f959bf).
Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #284   +/-   ##
=======================================
  Coverage   92.12%   92.12%           
=======================================
  Files          44       44           
  Lines        2146     2146           
  Branches      469      469           
=======================================
  Hits         1977     1977           
  Misses        169      169           

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

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

website/server/Dockerfile (1)

Line range hint 29-32: Consider using wget for health checks

curl is added as a dependency but only used for health checks. Consider using wget which is already included in Alpine Linux to reduce the image size.

 RUN apk add --no-cache \
     git \
-    ca-certificates \
-    curl
+    ca-certificates

Then update the health check command accordingly:

 HEALTHCHECK --interval=30s --timeout=30s --start-period=5s --retries=3 \
-    CMD curl -f http://localhost:8080/health || exit 1
+    CMD wget -q --spider http://localhost:8080/health || exit 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0d8ec45 and 5f959bf.

📒 Files selected for processing (4)

• .node-version (1 hunks)
• .tool-versions (1 hunks)
• website/client/Dockerfile (1 hunks)
• website/server/Dockerfile (2 hunks)

✅ Files skipped from review due to trivial changes (3)

• .tool-versions
• .node-version
• website/client/Dockerfile

⏰ Context from checks skipped due to timeout of 90000ms (9)

• GitHub Check: Build and run (windows-latest, 23.x)
• GitHub Check: Build and run (windows-latest, 22.x)
• GitHub Check: Build and run (windows-latest, 21.x)
• GitHub Check: Test (windows-latest, 22.x)
• GitHub Check: Build and run (windows-latest, 20.x)
• GitHub Check: Build and run (windows-latest, 19.x)
• GitHub Check: Build and run (windows-latest, 18.x)
• GitHub Check: Lint Renovate config
• GitHub Check: Cloudflare Pages

🔇 Additional comments (2)

website/server/Dockerfile (2)

Line range hint 47-48: Health check configuration looks good!

The health check implementation follows best practices with well-tuned parameters for production use.

---

4-4: 🛠️ Refactor suggestion

Consider pinning the specific Node.js version

While updating from node:22-alpine to node:23-alpine, consider explicitly pinning the version to 23.6.0 to prevent unexpected updates and ensure consistency with other configuration files.

-FROM node:23-alpine AS builder
+FROM node:23.6.0-alpine AS builder

Let's verify the Node.js version compatibility: