Update all dependencies #95
Conversation
It has reached the end of life - https:/nodejs/Release
|
@jsakas this should be considered a breaking change and requires a major version bump. every package that was working fine with v1.2.x and Node.js 6 is currently breaking because v1.3.0 is no longer compatible with Node.js 6. |
* ember-try: Fix broken `ember-data` dependency declarations `ember-data` is a monorepo now, so these kinds of version constraint declarations won't work anymore. see emberjs/data#6010 * CI: Use default dependencies for default scenarios The `latest` version of ember-data (v3.11) is using async/await in Node.js code, but since we run CI on Node.js 6 it does not support that yet. This means we will have to use an older version of ember-data for now until we drop support for Node.js 6. * CI: Allow failures for `ember-beta` scenario see previous commit about async/await usage in recent ember-data releases * package.json: Pin `cssstyle` to v1.2.x see jsdom/cssstyle#95 * package.json: Pin `ember-data` to v3.7.x Using `^3.0.0` currently resolves to v3.11.x which is not compatible with Node.js 6 anymore. v3.8.x and above have some other issues so we will use v3.7.x until we figure those out. * Revert "Build(deps-dev): bump mermaid from 7.1.2 to 8.0.0 (#1765)" This reverts commit 95ae7cb. Some dependencies of `mermaid@8` are incompatible with Node.js 6
|
@jsakas any chance of reverting the changes in 1.3.0 and releasing a new major? This causes downstream issues (in |
|
|
|
Sure, we'll drop it in the next major release. But that doesn't mean it should be dropped in a minor release of some transitive dependency |
|
Ah sorry yes, I read your comment too quickly. |
|
@SimenB seems like this is causing a lot of issues in the community, my apologies. What would be the proper way to resolve this? I'm thinking
Let me know. |
|
Yeah, doing those seems like the perfect fix! |
|
Oh, and maybe deprecate 1.3.0 saying it was an unintentional breaking change? No biggie either way, though 🙂 |
|
Thanks @SimenB - this is done. We now have v2.0.0 (master branch), and v1.4.0 (v1 branch) v1.3.0 has been deprecated on the npm registry. |
|
Thanks! |
Update all dependencies including CCSOM which looks like its gotten a few releases.
Drop support for Node 6. Its reached EOL - https:/nodejs/Release