Skip to content

chore: drop node 16 as it is EOL#225

Merged
yamadashy merged 1 commit intoyamadashy:mainfrom
chenrui333:drop-node-16
Dec 29, 2024
Merged

chore: drop node 16 as it is EOL#225
yamadashy merged 1 commit intoyamadashy:mainfrom
chenrui333:drop-node-16

Conversation

@chenrui333
Copy link
Contributor

Checklist

  • Run npm run test
  • Run npm run lint

Signed-off-by: Rui Chen <rui@chenrui.dev>
@bolt-new-by-stackblitz
Copy link

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Dec 29, 2024

📝 Walkthrough

Walkthrough

The pull request introduces changes to the project's Node.js version compatibility. The CI workflow configuration and package.json file have been updated to remove support for Node.js version 16.x. The modifications ensure that the project now targets Node.js versions 18.x, 20.x, 22.x, and 23.x, reflecting an update in the minimum required Node.js version from 16 to 18.

Changes

File Change Summary
.github/workflows/ci.yml Removed Node.js 16.x from test and build-and-run job matrices, now supporting 18.x, 20.x, 22.x, and 23.x
package.json Updated engine requirement from >=16.0.0 to >=18.0.0

Sequence Diagram

sequenceDiagram
    participant Dev as Developer
    participant CI as GitHub Actions
    participant Node as Node.js Runtime

    Dev->>CI: Push code
    CI->>Node: Select Node.js version
    Note over CI,Node: Versions: 18.x, 20.x, 22.x, 23.x
    CI->>CI: Run tests
    CI->>CI: Build project
    CI->>Dev: Report results
Loading

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
🪧 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
Copy link

codecov bot commented Dec 29, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.07%. Comparing base (0577e27) to head (3d92835).
Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #225   +/-   ##
=======================================
  Coverage   92.07%   92.07%           
=======================================
  Files          44       44           
  Lines        2058     2058           
  Branches      450      450           
=======================================
  Hits         1895     1895           
  Misses        163      163           

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

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🔭 Outside diff range comments (1)
.github/workflows/ci.yml (1)

Line range hint 143-143: Critical: Node.js 16.x needs to be removed from build-and-run job

The build-and-run job still includes Node.js 16.x in its version matrix, which is inconsistent with:

  1. The package.json engine requirement of ">=18.0.0"
  2. The test job's version matrix
  3. The PR objective to drop Node.js 16 support

This will cause CI failures as the build job attempts to run with an unsupported Node.js version.

Apply this fix:

       matrix:
         os: [ubuntu-latest, windows-latest, macos-latest]
-        node-version: [16.x, 18.x, 20.x, 22.x, 23.x]
+        node-version: [18.x, 20.x, 22.x, 23.x]
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 0577e27 and 3d92835.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (2)
  • .github/workflows/ci.yml (1 hunks)
  • package.json (1 hunks)
🔇 Additional comments (1)
.github/workflows/ci.yml (1)

95-95: LGTM on test job Node.js versions

The update to remove Node.js 16.x from the test matrix is appropriate.

@yamadashy
Copy link
Owner

yamadashy commented Dec 29, 2024

Hi, @chenrui333 !
Thank you for your continued contributions to Repomix!

You're right, Node.js 16 has reached its EOL. I initially kept it in the supported list because Repomix technically worked on it, but considering the security risks and overall maintenance, it's time to drop the support. This will be better for the project in the long run.

Thanks again for pointing this out and for creating the PR.
I'll merge this now.

@yamadashy yamadashy merged commit 316b894 into yamadashy:main Dec 29, 2024
@yamadashy
Copy link
Owner

@chenrui333
Thanks for helping with Node.js compatibility maintenance! I've included this change in Repomix v0.2.10:
https://github.com/yamadashy/repomix/releases/tag/v0.2.10

Hope to see more contributions from you in the future!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants