Skip to content

Restrict RC creation to versions with patch==0

David Diederich requested to merge restrict-rcs-on-patches into master

RC libraries are always made on the default branches, where the patch version should always be zero. These branches are building towards the next minor (or major) release, so it should have the form of x.y.0-SNAPSHOT.

If a change is intended to be part of a patch, it should first be merged into the default branch as x.y.0-SNAPSHOT, then cherry-picked into the release branch (release/a.b), where it will be built using the version a.b.n-SNAPSHOT (for the nth patch).

This change prevents the creation of the tag, library, and pipeline associated with an "rc" library if these expectations do not hold. Most likely, the artifact version was altered by mistake. Alternatively, this rc logic may need an update to handle previously unforeseen conditions.

Merge request reports