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

Update node minimum version to 10 per LTS retiring 8 #880

Closed
zachleat opened this issue Jan 23, 2020 · 2 comments
Closed

Update node minimum version to 10 per LTS retiring 8 #880

zachleat opened this issue Jan 23, 2020 · 2 comments
Labels
breaking-change This will have to be included with a major version as it breaks backwards compatibility. housekeeping

Comments

@zachleat
Copy link
Member

Node 8 is no longer being maintained.

https://nodejs.org/en/about/releases/

Marginally relevant to #678 if this happens before

@zachleat zachleat added the breaking-change This will have to be included with a major version as it breaks backwards compatibility. label Jan 23, 2020
@zachleat zachleat added this to the Next Major Version milestone Jan 23, 2020
@zachleat zachleat added this to Needs triage in Eleventy 1.0 via automation Feb 29, 2020
@Ryuno-Ki
Copy link
Contributor

@zachleat Do you consider this in 0.11.0 as well? Or only for stable release?

@zachleat zachleat modified the milestones: Planning for Eleventy v1.0.0, Eleventy 1.0.0 Sep 4, 2020
@zachleat
Copy link
Member Author

zachleat commented Sep 4, 2020

Fixed by cdb1191

@Ryuno-Ki this will ship with 1.0 (was not part of 0.11.0)

@zachleat zachleat closed this as completed Sep 4, 2020
Eleventy 1.0 automation moved this from Needs triage to Closed Sep 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking-change This will have to be included with a major version as it breaks backwards compatibility. housekeeping
Projects
No open projects
Eleventy 1.0
  
Closed
Development

No branches or pull requests

2 participants