fix(deps): update conventional changelog deps

[mlavina]

Description

This bumps the version to the latest major. The biggest change
was that it requires Node 6+ and since Lerna already requries
that this bump should not affect consumers.

Motivation and Context

See issue #1641

How Has This Been Tested?

I tried running npm run test locally, but start getting jest timeouts. Is there something I can do to get that fully test. I assume the PR will trigger some CI to test so many it's not needed?

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[mlavina]

tagging @hbetts as he was the one he released the changes to convetional-changelog to confirm that these changes are safe.

[hutson]

• conventional-changelog-angular changelog
• conventional-changelog-core was just the Node version bump.
• conventional-recommneded-bump was just the Node version bump.

The first package has changes in behavior that may effect Lerna users. Mostly it may change how commit messages are interpreted because of the changes to the angular convention, which is the default Lerna.

[mlavina]

@hbetts i removed my change for angular and only bumped recommended by 1 major since that major was only the node change

[evocateur]

Your lockfile changes are too broad, you appear to be using an old version of npm 5? It should not be removing the version ranges in the requires blocks. npm v5.10.0 or npm v6+ will properly update the lockfile.

[evocateur]

@hbetts Thanks for the clarification!

[mlavina]

I am using npm 5.5 it seems i'll update to latest npm and rebase this PR

[mlavina]

@evocateur I updated the package-lock with npm 6+. Is it good now?

[lock]

This thread has been automatically locked because there has not been any recent activity after it was closed. Please open a new issue for related bugs.