The breaking changes don’t really affect non deprecated platforms, so I don’t see a problem going with the major release directly.
El El mar, 7 may 2024 a las 14:18, Bryan Ellis <er...@apache.org> escribió: > Are there any objections if we change the target release to a major > release? > > The main changes currently in the branch are: > > - Added bundled resources for privacy manifest in iOS. > - Fixed electron to use the correct engine version 2.1.0 in package.json. > > Would the corrected engine version necessitate a minor release, considering > we typically don't backport changes? If it isn't necessary, I might not > find any reasons to object to proceeding with a major release. > > > > On Tue, May 7, 2024 at 7:01 PM julio cesar sanchez <jcesarmob...@gmail.com > > > wrote: > > > I have two pending PRs, but they are breaking (removing deprecated > > platforms and unused code), so if they get merged, the release would be > > 3.0.0. not 2.2.0 > > > > El mar, 7 may 2024 a las 7:17, Bryan Ellis (<er...@apache.org>) > escribió: > > > > > Does anyone have any reason to delay a release for > cordova-plugin-device? > > > > > > * cordova-plugin-device (2.2.0) > > > > > > > > > https://github.com/apache/cordova-plugin-device/compare/rel/2.1.0...master > > > > > > Any additional outstanding changes to land? > > > > > > If not, I will start the release process shortly > > > > > >
