Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use nodejs 20 instead of nodejs 19 in ci #618

Merged
merged 1 commit into from
Aug 7, 2023
Merged

Conversation

JakeChampion
Copy link
Contributor

Node.js 19 has become unsupported, Node.js 20 is supported, let's use that

Major Node.js versions enter Current release status for six months, which gives library authors time to add support for them. After six months, odd-numbered releases (9, 11, etc.) become unsupported, and even-numbered releases (10, 12, etc.) move to Active LTS status and are ready for general use. LTS release status is "long-term support", which typically guarantees that critical bugs will be fixed for a total of 30 months. Production applications should only use Active LTS or Maintenance LTS releases.
https://nodejs.dev/en/about/releases/

Node.js 19 has become unsupported, Node.js 20 is supported, let's use that 

>Major Node.js versions enter Current release status for six months, which gives library authors time to add support for them. After six months, odd-numbered releases (9, 11, etc.) become unsupported, and even-numbered releases (10, 12, etc.) move to Active LTS status and are ready for general use. LTS release status is "long-term support", which typically guarantees that critical bugs will be fixed for a total of 30 months. Production applications should only use Active LTS or Maintenance LTS releases.
>https://nodejs.dev/en/about/releases/
@JakeChampion JakeChampion merged commit a029aff into main Aug 7, 2023
81 checks passed
@JakeChampion JakeChampion deleted the jake/node-20 branch August 7, 2023 17:13
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.

None yet

2 participants