scap/utils.py · master · repos / releng / Scap

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.

How to register an account on GitLab. Due to spam, new accounts are locked until approved by an admin or the approver bot. Your GitLab account gets automatically approved within one hour if you are a member of Trusted Contributors in Gerrit, or a member of the Trusted-Contributors group in Phabricator and linked your Developer account to your Phabricator account. If none of these apply, you can file an unlock request to expedite access.

Support: mw:GitLab, how to host a project on GitLab, #wikimedia-gitlab on libera.chat, #GitLab on Phabricator.

Blame History

utils.py: Handle "next" version · 481a93c0

Ahmon Dancy authored Jul 17, 2024

Update `parse_wmf_version()` and `version_argument_parser()` to handle
the "next" version (corresponding to the `wmf/next` branch).

Bug: T369112
Change-Id: Ifbcd4aa5eb9a14de82c211811342df6cd933491c

481a93c0

Admin message

Admin message

Admin message