GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens, and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption in our documentation.

Self sign-up has been disabled due to increased spam activity. If you want to get access, please send an email to a project owner (preferred) or at gitlab(at)nic(dot)cz. We apologize for the inconvenience.

make-archive: consider removing dangerous -v option

What is the use-case for this option? I'm afraid this option only leads to confusion and unexpected behaviour and I'd completely remove it.

Possible issues:

only the archive is renamed, which doesn't really change the tarball structure (i.e. the directory inside archive still uses development version)
it can lead to creation of non-existent versions, or using a development version when intending to use a released version
when cache is used (default), it won't actually rename/recreate the development archive already created

Overall, this seems to be too much trouble for very little use/benefit.