<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "bug" label: - https://gitlab.com/gitlab-org/cli/-/issues/?label_name%5B%5D=type%3A%3Abug and verify the issue you're about to submit isn't a duplicate. ---> ### Summary The [generic CI linter](https://docs.gitlab.com/ee/api/lint.html#validate-the-ci-yaml-configuration) for GitLab is [going away in 16.0](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/103853). The [new endpoint](https://docs.gitlab.com/ee/api/lint.html#validate-a-ci-yaml-configuration-with-a-namespace) will require a namespace/project to work. This will cause problems with `glab ci lint` as it's using the old endpoint. ### Possible Solutions * We could put a future deprecation message in for `glab ci lint` * Eventually require `glab ci lint` to need a namespace. We could probably infer it from the project it's in using another API call? <!-- If you can, link to the line of code that might be responsible for the problem -->