-
-
Notifications
You must be signed in to change notification settings - Fork 157
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support GitLab's new style routes #266
Comments
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? |
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:
|
That's not how URLs are supposed to work; old URLs are never supposed to stop working. |
I agree but unfortunately it's happening source |
Gitlab returned the redirection, it seems to work fine now! |
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.
The text was updated successfully, but these errors were encountered: