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

Docs: Fix Node.js 6 EOL date #11676

Merged
merged 1 commit into from May 5, 2019

Conversation

Projects
None yet
5 participants
@Cherry
Copy link
Contributor

commented May 4, 2019

What is the purpose of this pull request? (put an "X" next to item)

[x] Documentation update
[ ] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofixing to a rule
[ ] Add a CLI option
[ ] Add something to the core
[ ] Other, please explain:

What changes did you make? (Give an overview)

Node.js 6 went EOL in April 2019, as per https://github.com/nodejs/Release#end-of-life-releases. This looks like a simple typo.

Docs: Fix Node 6 LTS EOL date
Node.js 6 went EOL in April 2019, not 2018
@jsf-clabot

This comment has been minimized.

Copy link

commented May 4, 2019

CLA assistant check
All committers have signed the CLA.

@eslint eslint bot added the triage label May 4, 2019

@Cherry Cherry changed the title Docs: Fix Node 6 LTS EOL date Docs: Fix Node.js 6 EOL date May 4, 2019

@g-plane

g-plane approved these changes May 4, 2019

@platinumazure platinumazure merged commit f2e7828 into eslint:master May 5, 2019

5 checks passed

commit-message Commit message follows guidelines
Details
continuous-integration/appveyor/pr AppVeyor build succeeded
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details
licence/cla Contributor License Agreement is signed.
Details
release-monitor No patch release is pending
Details
@platinumazure

This comment has been minimized.

Copy link
Member

commented May 5, 2019

Merged, thanks for contributing!

@Cherry Cherry deleted the Cherry:patch-1 branch May 5, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.