nightly is just master on any given 'night' right? We don't want to update dependent versions of everything all the time ...
I think, if anything, what is needed is an overall test of all the pieces together, but I don't think this means modifying every package.json of every module every night. If we wanted more flexibility, maybe the git-master version of each package.json points at the git-master of each other module ... but I don't think this helps us. I think is is best to just expect that things are going to break, and we will have to resolve dependencies when we choose to release. @purplecabbage risingj.com On Wed, Sep 12, 2018 at 1:27 PM Oliver Salzburg <oliver.salzb...@gmail.com> wrote: > On 2018-09-12 21:29, Chris Brody wrote: > > I think this would give us better integrity of nightly builds. > > I don't think I understand the proposal. > > If the goal is to produce nightly builds, why not change the dependency > version during the nightly build, publish the nightly and leave master > dependent on the stable dependency? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org > >
