Uniqueness constraint missing in the Release model
It is possible to have the same tag (eg. v1.2
) for two or more releases associated to the same project.
This situation occurred over multiple projects on gitlab.com
. As of now, there are 96 instances of releases on gitlab.com
with the same project_id
and tag
.
The master branch was also broken a few weeks ago, as a result of this situation.
We need to:
- add a uniqueness constraint to the Release model
- rename the release tag for the concerned records on
gitlab.com
(TBC)
Edited by Etienne Baqué