In flutter projects, it is usual to increase the build number when increasing the version.
This is necessary because the google playstore will only recognize build number versioning and regards everything else as flavour.
Build numbers are therefore basically a count of how many versions have been released, but arent very useful to include with the actual version number.
My pubspec therefore does have a build number, but it is completely irrelevant to the changelog and its readers.
When I use
cider release
my build number is also included in the Changelog, which I see as undesirable.
I am not sure what the best course of action would be to acommodate for this usecase in the package.
But I would be delighted if it would be possible to resolve this in some way.
Maybe the command could provide an option for not including the build number when transfering the version.
Perhaps it would be useful in general to be able to specify the behaviour for how build numbers are treated by default in the config file, as right now I will always have to use --bump-build together with cider bump.
closing this as I realized I need the build number to automatically generate android changelogs and therefore omitting it wouldnt be useful to me anymore.
In flutter projects, it is usual to increase the build number when increasing the version. This is necessary because the google playstore will only recognize build number versioning and regards everything else as flavour. Build numbers are therefore basically a count of how many versions have been released, but arent very useful to include with the actual version number.
My pubspec therefore does have a build number, but it is completely irrelevant to the changelog and its readers. When I use
my build number is also included in the Changelog, which I see as undesirable.
I am not sure what the best course of action would be to acommodate for this usecase in the package. But I would be delighted if it would be possible to resolve this in some way.
Maybe the command could provide an option for not including the build number when transfering the version.
Perhaps it would be useful in general to be able to specify the behaviour for how build numbers are treated by default in the config file, as right now I will always have to use
--bump-build
together withcider bump
.