release api incorrectly complaints about 'must follow semantic version' (and GUI)
I've been using the release API (via release-cli) for a few years. I've also used the same pattern for releases for years, namely by using the tag format v1.2.3
. For the generic packages, I have to remove the v
btw, as the generic packages API doesn't allow the leading v
(there's an existing issue for that).
Since a few days, I'm getting the following error from the release API.
time="2024-02-18T14:03:13Z" level=info msg="Creating Release..." cli=release-cli command=create name="Release of KiCi v0.4.2" project-id=54208556 ref=cc2032ee120d036ec917532144ac088e2ceecbe5 server-url="https://gitlab.com" tag-message= tag-name=v0.4.0 version=0.16.0
time="2024-02-18T14:03:15Z" level=fatal msg="run app" cli=release-cli error="failed to create release: API Error Response status_code: 400 message: Validation failed: must follow semantic version" version=0.16.0
See https://gitlab.com/ci-includes/kici/-/jobs/6177392292 (but also https://gitlab.com/ci-includes/kici/-/jobs/6193730704) where this is being triggered.
So what makes me think this isn't my own fault (which of course could still be the case),
time="2024-02-10T16:45:27Z" level=info msg="release created successfully!" cli=release-cli command=create name="Release of KiCi v0.3.3" project-id=54208556 ref=8aabe7f698146b2609de491eda23b98fcd81e3d3 server-url="https://gitlab.com" tag-message= tag-name=v0.3.3 version=0.16.0
Was run only a few days ago, and it's fine. Note how the tag follows the same pattern. (https://gitlab.com/ci-includes/kici/-/jobs/6143742372 for the original run of the pipeline).
The only thing that could be contributing to this issue, is that v0.4.2 as a tag was pushed several times (force push), but no release was successfully created (I thought that may have been an issue, as v0.4.1 was created at some point, but I overwritten it by deleting the release).
So unless this is a bug on my side, this is probably a change breaking builds making this a severity2 at the least.
Going to the tags screen, trying to create a release also fails with the same error message, making this probably a severity1 ...