Update from code changes: note Pro+ plan for self-hosted GitLab OAuth - #6972
Open
mintlify[bot] wants to merge 1 commit into
Open
Update from code changes: note Pro+ plan for self-hosted GitLab OAuth#6972mintlify[bot] wants to merge 1 commit into
mintlify[bot] wants to merge 1 commit into
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Registering a self-hosted GitLab OAuth application and starting the authorization flow now requires a Mintlify organization on the Pro plan or higher; Hobby and trial orgs receive a 403. Existing self-hosted GitLab installations continue to work and can re-authorize as normal. Added a plan-requirement bullet to the prerequisites of the self-hosted GitLab OAuth guide and mirrored the change to the Spanish, French, and Chinese translations. Triggered by https://github.com/mintlify/server/pull/7498.
Changes
deploy/gitlab-self-hosted.mdx: added Pro+ plan prerequisite.es/deploy/gitlab-self-hosted.mdx,fr/deploy/gitlab-self-hosted.mdx,zh/deploy/gitlab-self-hosted.mdx: translated updates.Note
Low Risk
Documentation-only updates to deployment guides; no application code or security behavior changes in this repo.
Overview
Documents that self-hosted GitLab OAuth setup now requires a Mintlify organization on the Pro plan or higher. Hobby and trial orgs get a 403 when registering OAuth credentials or starting authorization.
Adds this as a new prerequisites bullet in
deploy/gitlab-self-hosted.mdxand mirrors the same wording in the Spanish, French, and Chinese guides. Notes that orgs with existing self-hosted GitLab installs from before the requirement keep working and can re-authorize normally.Reviewed by Cursor Bugbot for commit 0e66bb5. Bugbot is set up for automated code reviews on this repo. Configure here.