"Create release" button in gitlab leads to 404 page

Adding onto this: those of us developing Gitlab components will will want this feature to be available on GitLab per https://docs.gitlab.com/ee/ci/components/#publish-a-new-release

This may be another reason to embrace 🌱 [META] Use GitLabCI for packaging Postponed unless we wish to have edge processing to determine if a redirect should occur.

Can gitlab be made aware of the node ID of the project

GitLab does not have that sort of customization, nothing like Drupal’s fields or modules. So it is up to Drupal.org to do the redirecting.

The current redirection is something like this:
- "Create release link": https://git.drupalcode.org/project/config_notify/-/releases/new?tag_name...
- 301 to https://www.drupal.org/project/config_notify/releases/new → , which 404s

We could create a menu path like project/%machine_name/releases/new, and from that, fetch the project with that machine_name and redirect to https://www.drupal.org/node/add/project-release/NID →

The logic might be a bit trickier since machine_name does not need to be the same as the repository name.

---

Another option, since releases are fully managed via drupal.org, might be to turn off "Releases" for all projects (https://gitlab.com/gitlab-org/gitlab/-/merge_requests/96373)