CI: Change Node.js to v6

[mike-north]

This library depends on [email protected], which requires node 6 or above

[Turbo87]

@mike-north please don't merge code without review. This PR is missing the engine bump in package.json.

[mike-north]

@Turbo87 I'll refrain from merging in these pure CI config fixes, and any other changes in the future. Several simplabs pipelines have been failing on master for up to 1 month -- thought that these changes would be welcomed and a "no brainer" thing to go in.

[Turbo87]

thought that these changes would be welcomed and a "no brainer" thing to go in.

don't get me wrong, these PRs are very welcome, just please ping any of us to get a review before merging yourself 🙏

[Turbo87]

This library depends on [email protected]

I've just checked this. The problem is that we use [email protected] as a dev dependency, which depends on testem@2 which depends on execa@1. The addon itself should still work fine on Node 4 though, but I'll go ahead and bump the supported version in the package.json (#35) to unblock some of the dependabot PRs and then release a v0.4.0.

[mike-north]

The problem is that we use [email protected] as a dev dependency, which depends on testem@2 which depends on execa@1

This was my original basis for only bumping the version up in CI, and leaving package.json engines alone. I don't believe that we need to force any consumer off node4, although we do need to test on node6+.

[Turbo87]

yeah, but it seems unfortunate to test on a higher Node version than what we support. an alternative would be to revert to [email protected] (I think...), which still uses testem@1 and does not have that execa@1 dependency, but dropping Node 4 support is probably the best way forward anyway. For users that still need Node 4 support I've added a v0.3.x branch to the repo, where we could do the CLI downgrade if needed.