chore: upgrade conventional commits

[icco]

This closes the following:

• PRs: chore(deps): update dependency conventional-changelog-conventionalcommits to v8 #632, conventional-changelog-conventionalcommits v8.0.0 breaks semantic release #633, chore(deps): update dependency conventional-changelog-ember to v5 #634, chore(deps): update dependency conventional-changelog-eslint to v6 #635, chore(deps): update dependency conventional-changelog-express to v5 #636, chore(deps): update dependency conventional-changelog-jshint to v5 #637, fix(deps): update dependency conventional-changelog-angular to v8 #638, fix(deps): update dependency conventional-changelog-writer to v8 #639
• As suggested by RangeError: Invalid time value conventional-changelog/conventional-changelog#1267

[travi]

Please make sure our tests are passing. npm test should be enough to verify this locally.

[travi]

Please keep dev dependencies pinned to specific versions

[travi]

Please make sure our tests are passing. npm test should be enough to verify this locally.

@icco the tests continue to fail after your follow up to pin the dev dependencies. are you interested in working through the breaking changes related to these updates in order to help us move this forward?

[icco]

Please make sure our tests are passing. npm test should be enough to verify this locally.

@icco the tests continue to fail after your follow up to pin the dev dependencies. are you interested in working through the breaking changes related to these updates in order to help us move this forward?

Yeah been trying to get the tests pass locally with no luck. I believe there's an underlying bug in the import plugin you use but can not figure it out.

[travi]

appreciate the update and the investigation. we are starting to investigate as well, but unsure how much time we can dedicate soon. please feel free to keep us up to date if you make progress, even if that means pushing wip changes that dont get to a point of getting tests to a passing state.

it could also be helpful to start with running the integration tests (npm run test:integration) first for a larger scope feedback loop before getting distracted by the unit tests (npm run test:unit) if the interface changes are unclear.

[travi]

appreciate the investment here, but closing in favor of #643. we could still use help updating the commit-analyzer plugin in similar ways in case you are still interested and the other PR helps with any complexities that you encountered with this effort