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.

Sign up for GitHub

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

Jump to bottom

Remove Node 18 across all of cmfive #257

Open
chris-bateman opened this issue Feb 18, 2024 · 1 comment
Open

Remove Node 18 across all of cmfive #257

chris-bateman opened this issue Feb 18, 2024 · 1 comment
Assignees
@adam-buckley @mattbell87
Labels
dependencies Pull requests that update a dependency file help wanted
Milestone
Node 18 EOL

Comments

@chris-bateman
Copy link
Member

Remove Node 18 across all of cmfive in favour of Node 20.

Node 18 lacks active support but still has one year of security support.
image

Limiting the project to Node 20 and the latest node (For future proofing) reduces the CI complexity and ensures deployments are consistent with a single LTS version.

Legacy clients don't get updates, so removing Node 18 from active branches should be ok.
@chris-bateman chris-bateman added help wanted dependencies Pull requests that update a dependency file labels Feb 18, 2024
@chris-bateman
Copy link
Member Author

On hold until closer to EOL date

@chris-bateman chris-bateman added this to the Node 18 EOL milestone Feb 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@adam-buckley adam-buckley

@mattbell87 mattbell87

Labels
dependencies Pull requests that update a dependency file help wanted
Projects
None yet
Milestone
Node 18 EOL
Development

No branches or pull requests
5 participants
@adam-buckley @mattbell87 @chris-bateman @DerekCrannaford @Dane-2pi