On 2018-09-13 00:34, Chris Brody wrote:
In case of major version bump each Cordova package will continue to
keep dependency on previous patch release of other packages until we
make the new release.
Reading this makes me think I didn't understand an important part of the
discussion. Isn't this basic semantic versioning?
If you have a 1.x of your main package, you want to release 2.x and you
have a dependency of which you want to include a newer version than is
covered by your current semver range, then update the range in your
package.json before you release 2.x.
There is also nothing wrong with bumping dependency semver ranges in a
module in master. Then you can install the new dependency version when
you pull the latest changes and update your dependencies. This should
obviously only be done when there was an important change in the
dependency that is required in master.
This seems very obvious and is covered thoroughly in at least the
documentation of npm. What am I missing?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org
