Support GitLab's new style routes

[Reddine]

GitLab started moving routes under the - scope around version 12.0. You can find more information about this change in the GitLab issue #28848.

Paths without the - are considered legacy and can be found in older versions. Starting from version 16, which was released yesterday (May 18, 2023) GitLab FOSS Changelog, all group/project routes are only accessible through the /-/ path.

This change has affected the generated autochangelog for projects that use GitLab. Users will encounter an HTTP error 404 - Page Not Found when accessing these routes.

[ljharb]

Cool URLs don't change; if a link that used to work stops working then GitLab has broken one of the core principles of the web - or are you saying that new links don't work, and the autogeneration is producing the old style?

[Reddine]

Yes, they used to function properly due to the redirection to the corresponding new links, but that is no longer the case since version 16.0.

The autogenearation is producing the old style which were defined as legacy URLs.

According to the release notes it seems a necessitated choice! I quote from https://gitlab.com/gitlab-org/gitlab/-/issues/28848:

We are removing legacy URLs from the GitLab application. The introduction of subgroups in GitLab 9.0 necessitated that we use a /-/ delimiter in URLs to signify the end of a group path. More information about this change can be found at #214217. Since then, we've been consolidating all of the URLs in GitLab to use this delimiter for project, group, and instance-level features. URLs which do not use the delimiter are being removed in GitLab 16.0 in favor of those that do.

[ljharb]

That's not how URLs are supposed to work; old URLs are never supposed to stop working.

[Reddine]

I agree but unfortunately it's happening source

[Reddine]

Gitlab returned the redirection, it seems to work fine now! Discussion can be followed on https://gitlab.com/gitlab-org/gitlab/-/issues/412435