I agree that this kind of situation should be addressed by a proper release of the dependency. If it's a breaking change, so be it. I don't mind if we have cordova-common 23.5.7 in a year from now.
Am Mi., 12. Sep. 2018 um 22:44 Uhr schrieb Oliver Salzburg < oliver.salzb...@gmail.com>: > On 2018-09-12 22:40, Jan Piotrowski wrote: > > cordova-create uses cordova-common and cordova-fetch. Right now two > > existing releases are pinned as dependencies. cordova-common and > > cordova-fetch have changes in master, that are necessary for new > > things in cordova-create to work. Right now there is no way to change > > cordova-create to do this. Using nightly of cordova-comand and > > cordova-fetch would enable this. Correct? > > Why not just publish the new version? I mean, properly, not a -nightly. > > Then the projects could depend on these new versions on work properly in > master as well. > > For the time being, the -nightly release would work fine for the > purpose, but something like that should be occasional, not regular. I > believe the latter case would produce more failures than it solves. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org > >
