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

Bump minimum node version. #21

Merged
merged 2 commits into from
Dec 1, 2016
Merged

Bump minimum node version. #21

merged 2 commits into from
Dec 1, 2016

Conversation

wtgtybhertgeghgtwtg
Copy link
Contributor

Now requires node 0.12 or greater. Drops pinkie-promise.

@SBoudrias SBoudrias merged commit e778147 into SBoudrias:master Dec 1, 2016
@wtgtybhertgeghgtwtg wtgtybhertgeghgtwtg deleted the node-version branch December 1, 2016 19:16
@not-an-aardvark
Copy link

Shouldn't this have been published as a new major version? It caused the generator-eslint build to start failing when run-async@2.3.0 was released, since we still support Node v0.10 and run our tests on it.

I realize that Node v0.10 is now unsupported by the Node.js project, and we do plan to stop supporting it relatively soon, but dropping support for a Node version is a backwards-incompatible change and should result in a major version bump.

@platinumazure
Copy link

@SBoudrias Any chance this could be reverted, published as 2.3.1, and then the commit can be re-applied and released as 3.0.0? Otherwise, we'll have to add run-async@2.2.x as a dependency for our build, which is a little silly.

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.

4 participants