Closed bheemvennapureddy closed 10 months ago
Your workflow would include promotion of the v1.1.0 to release from pre-release? Or do you intend to force push the v1.1.0 tag with fixes? How about changing your pre-release to include a pre-release identifier? Release drafter is behaving as intended. It will ignore pre-releases to create a full draft for a given release.
In any case please check the readme as it might have the config options you are looking for ☺️
Your workflow would include promotion of the v1.1.0 to release from pre-release? Or do you intend to force push the v1.1.0 tag with fixes?
Our intention is to promote v1.1.0 to latest ( prod release ) from prerelease but there were road blocks on the way with either infra or testing , so we want a new draft which is a increment from the previous draft has all the changes along with a fix.
So the next prerelease draft should be v1.1.1 than being a duplicate of v1.1.0
Release drafter is behaving as intended. It will ignore pre-releases to create a full draft for a given release.
Apart from including a prerelease identifier i don't see a way to work around this.
https://github.com/release-drafter/release-drafter#configuration-options did you check out ?
Perhaps include-pre-releases
is what you are looking for?
@jetersen makes sense that sounds about right - if i do so the change log is not pulling up all the log from previous pre-release which kind of makes sense
@jetersen Quick question so the minor version will not be incremented even if we have include-pre-releases and prerelease set to true
Sorry there was a typo.
Our use case is
Issue duplicate draft tags with prerelease.
Is there a way we can increment prerelease without any identifier ?