Patch releases: Detect if no security fixes are available on the next patch
&1193 (closed) made patch releases to be SLO-driven, in consequence, patch releases are scheduled twice a month around the monthly release date. With this frequent cadence, there might be a case where a version doesn't include any security fixes. In this scenario, release-tools should be smart enough to detect there are no specific security fixes and adjust the release/task issue respectively.
Adjustments required to the release/task issue:
- The "Two days before due date" section should be dropped
- The "One day before the due date" section should be dropped
- Tags and publish commands should be updated to drop the
--security
flag - The
version
should be created withSecurity release?: No
Edited by Mayra Cabrera