-
Notifications
You must be signed in to change notification settings - Fork 64
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
[Plugins] Drop Node 4 support #72
Comments
Part of apache/cordova#72 <!-- Please make sure the checklist boxes are all checked before submitting the PR. The checklist is intended as a quick reference, for complete details please see our Contributor Guidelines: http://cordova.apache.org/contribute/contribute_guidelines.html Thanks! --> ### Platforms affected n/a - development ### Motivation and Context <!-- Why is this change required? What problem does it solve? --> <!-- If it fixes an open issue, please link to the issue here. --> Drops EOL Node.js 4 from CI config. BREAKING CHANGE! :) ### Description <!-- Describe your changes in detail --> see above. ### Testing <!-- Please describe in detail how you tested your changes. --> TravisCI and Appveyor test results. ### Checklist - [ ] I've run the tests to see all new and existing tests pass - [ ] I added automated test coverage as appropriate for this change - [ ] Commit is prefixed with `(platform)` if this change only applies to one platform (e.g. `(android)`) - [ ] If this Pull Request resolves an issue, I linked to the issue in the text above (and used the correct [keyword to close issues using keywords](https://help.github.com/articles/closing-issues-using-keywords/)) - [ ] I've updated the documentation if necessary
Part of apache/cordova#72 <!-- Please make sure the checklist boxes are all checked before submitting the PR. The checklist is intended as a quick reference, for complete details please see our Contributor Guidelines: http://cordova.apache.org/contribute/contribute_guidelines.html Thanks! --> ### Platforms affected n/a - development ### Motivation and Context <!-- Why is this change required? What problem does it solve? --> <!-- If it fixes an open issue, please link to the issue here. --> Drops EOL Node.js 4 from CI config. BREAKING CHANGE! :) ### Description <!-- Describe your changes in detail --> see above. ### Testing <!-- Please describe in detail how you tested your changes. --> TravisCI and Appveyor test results. ### Checklist - [ ] I've run the tests to see all new and existing tests pass - [ ] I added automated test coverage as appropriate for this change - [ ] Commit is prefixed with `(platform)` if this change only applies to one platform (e.g. `(android)`) - [ ] If this Pull Request resolves an issue, I linked to the issue in the text above (and used the correct [keyword to close issues using keywords](https://help.github.com/articles/closing-issues-using-keywords/)) - [ ] I've updated the documentation if necessary
Due to major releases (Cordova CLI v9, cordova-android v8, cordova-ios v5) I've unchecked all plugins since the CI won't work currently with those outdated Xcode images nor the unchecked licenses for Android SDKs. First candidate to cleanup this, too, is: apache/cordova-plugin-vibration#76 For reference, broken TravisCI builds: https://travis-ci.org/apache/cordova-plugin-vibration/jobs/523723056#L2302 & https://travis-ci.org/apache/cordova-plugin-vibration/jobs/523723055#L2209 |
I would not favor supporting Node.js version 6 for much longer, considering that its scheduled EOL is just a few days away. |
+1 that’s what I’ve though of, too :) |
I'll copy over what I wrote at apache/cordova-plugin-vibration#76 (comment):
When we have that (currently tests are failing on iOS 12.2 - not sure if this is a problem with the plugin or with the test setup yet) and vibration in a good state, we can start rolling that out to more plugins and see what happens. |
travis.yml changes have been created as PRs for all plugins. This included going to node 6 for all of these configurations. I wrote a dev mailing list message which gives an overview: https://lists.apache.org/thread.html/959ebe1683ac8ac10013d70a514bdf213ac6935ffd28fd045b269ab6@%3Cdev.cordova.apache.org%3E Now we probably only need PRs for appveyor.yml and possibly updated to package.json. |
Plugins were released with green CI, so this should already be taken care of for all plugins - correct? If not, now would be a good time to create the PRs. |
@janpio I did a quick review though those remaining plugin's master branch and this is the results: Completed and can be updated in ticket desc.
Unfinished and need PRs
AppVeyor could actually be bumped to node 8 to match with Travis CI configs. If that is preferred, then camera and maybe the already completed items would need revisits. |
Closing in favor of #79 |
Part of apache/cordova#72 <!-- Please make sure the checklist boxes are all checked before submitting the PR. The checklist is intended as a quick reference, for complete details please see our Contributor Guidelines: http://cordova.apache.org/contribute/contribute_guidelines.html Thanks! --> ### Platforms affected n/a - development ### Motivation and Context <!-- Why is this change required? What problem does it solve? --> <!-- If it fixes an open issue, please link to the issue here. --> Drops EOL Node.js 4 from CI config. BREAKING CHANGE! :) ### Description <!-- Describe your changes in detail --> see above. ### Testing <!-- Please describe in detail how you tested your changes. --> TravisCI and Appveyor test results. ### Checklist - [ ] I've run the tests to see all new and existing tests pass - [ ] I added automated test coverage as appropriate for this change - [ ] Commit is prefixed with `(platform)` if this change only applies to one platform (e.g. `(android)`) - [ ] If this Pull Request resolves an issue, I linked to the issue in the text above (and used the correct [keyword to close issues using keywords](https://help.github.com/articles/closing-issues-using-keywords/)) - [ ] I've updated the documentation if necessary
As per #5, but this time for plugins:
Goal
List of active core plugins
The text was updated successfully, but these errors were encountered: