Should updating the dependencies to newer versions really part of a release?
(if not flagged via npm audit)
It introduces so many ways stuff could break and when its changed during the release process, it practically guarantees that it has not been used/tested at all.
This is regarding https://github.com/apache/cordova-coho/blob/master/docs/platforms-release-process.md#check-dependencies and https://github.com/apache/cordova-coho/blob/master/docs/platforms-release-process.md#resolve-any-outdated-dependencies (and equivalents in other release processes)
Should updating the dependencies to newer versions really part of a release? (if not flagged via
npm audit)It introduces so many ways stuff could break and when its changed during the release process, it practically guarantees that it has not been used/tested at all.