-
Notifications
You must be signed in to change notification settings - Fork 24
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
drop 0.12? #55
Comments
Closed
Swagger 3.0 says (per #70)
|
Yes, let's drop support for 0.12 when we go to 4.x |
srl295
added a commit
to srl295/gp-js-client
that referenced
this issue
Aug 2, 2017
* add engines in package.json * add a 'news' item to the README. In support of IBM-Cloud#55
srl295
added a commit
to srl295/gp-js-client
that referenced
this issue
Aug 2, 2017
Supporting: IBM-Cloud#55
|
srl295
added a commit
to srl295/gp-js-client
that referenced
this issue
Aug 2, 2017
* add engines in package.json * add a 'news' item to the README. In support of IBM-Cloud#55
srl295
added a commit
to srl295/gp-js-client
that referenced
this issue
Aug 2, 2017
Supporting: IBM-Cloud#55
srl295
added a commit
to srl295/gp-js-client
that referenced
this issue
Aug 28, 2017
* bump version to v2.0.0-0 * drop Node v0.12 from travis and package.json No actual breaking changes here, but get ready. Fixes: IBM-Cloud#55
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
would be nice to use some later, esp ES6 features. We could go the babel route etc of course.
This would be a semver-major breaking change, of course. So those who need 0.12 support could continue to use the v1.x line
The text was updated successfully, but these errors were encountered: