Skip to content

Conversation

@getty104
Copy link
Member

@getty104 getty104 commented Apr 3, 2025

What

  • パッケージのサポートとしてNode.js v18を落とす

How

  • nodeのサポートバージョンを>=20.0.0に変更

Why

Refs

AI Summary

This pull request includes updates to the Node.js versions used in the project configuration files. The most important changes include updating the Node.js versions in the GitHub Actions workflow and the package.json file.

Updates to Node.js versions:

  • .github/workflows/test.yml: Updated the Node.js versions in the matrix strategy to include 20.0.0 and removed 18.18.0 and 18.20.4.
  • package.json: Updated the minimum required Node.js version to >=20.0.0.

Copilot AI review requested due to automatic review settings April 3, 2025 07:09
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This pull request updates the project configuration to drop support for Node.js v18 and require Node.js v20 or above. The key changes include:

  • Removal of Node.js v18 versions from the testing matrix.
  • Addition of Node.js v20 version in the GitHub Actions workflow file.
Files not reviewed (1)
  • package.json: Language not supported

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Hello @getty104, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

Summary of Changes

This pull request drops support for Node.js v18 and updates the minimum required Node.js version to v20.0.0. This change is in response to an update in a related project (qiita-cli) that necessitates a newer Node.js version.

Highlights

  • Node.js Version Update: The minimum required Node.js version has been updated from v18.18.0 to v20.0.0 in package.json.
  • GitHub Actions Workflow Update: The GitHub Actions workflow configuration has been updated to use Node.js v20.0.0 and v20.x, removing v18.x versions.

Changelog

  • package.json
    • Updated the engines.node field to require Node.js version >=20.0.0.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.


Node's versions, they come and go,
Eighteen retires, twenty will grow.
Dependencies shift,
Code must uplift,
A newer engine starts the show.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request drops support for Node.js v18 and updates the supported version to >=20.0.0. The changes include updates to the package.json file and the GitHub Actions workflow. Overall, the changes seem straightforward and necessary for keeping the project up-to-date with supported Node.js versions.

Merge Readiness

The pull request appears to be ready for merging, as it involves a simple update to the supported Node.js version. I am unable to directly approve the pull request, and recommend that others review and approve this code before merging.

Comment on lines 87 to +88
"engines": {
"node": ">=18.18.0"
"node": ">=20.0.0"

Choose a reason for hiding this comment

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

medium

Consider adding a more specific version range, such as ^20.0.0 instead of >=20.0.0. This indicates that the project is tested and compatible with any version 20.x.x, but might not be compatible with version 21 and above. This can help prevent unexpected issues when newer Node.js versions are released.

If the project is indeed compatible with newer versions, then the current implementation is fine.

"node": "^20.0.0"

@getty104 getty104 self-assigned this Apr 3, 2025
@getty104 getty104 requested a review from ohakutsu April 3, 2025 07:13
Copy link
Member

@ohakutsu ohakutsu left a comment

Choose a reason for hiding this comment

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

LGTM!

@getty104 getty104 merged commit 83116c8 into main Apr 4, 2025
6 checks passed
@getty104 getty104 deleted the drop-support-v18 branch April 4, 2025 02:13
@ohakutsu ohakutsu mentioned this pull request Dec 9, 2025
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.

3 participants