Repository navigation
Update from code changes: third-party libraries and protected previews - #7952
Merged
Merged
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
dks333
approved these changes
Oct 21, 2026
ethanpalm
approved these changes
Oct 22, 2026
This was referenced Oct 22, 2026
This branch was successfully deployed
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
2 participants
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.
Clarifies on the third-party libraries page that the authentication restriction also covers preview deployments protected by organization authentication or a password, and that you can't turn on authentication, personalization or preview access restrictions while the site uses packages.
Mintlify now enforces the packages and authentication block on every path that turns on access control: protected previews of a public site fail to deploy when packages are in use, and turning on preview protection returns a conflict error instead of succeeding.
Based on a merged backend change that enforces the npm packages authentication block on every authentication path, including preview deployments.
Duplicate check: no open docs PRs by the author, Ethan Palm or bots mention packages, third-party libraries or preview authentication, and nothing merged in the last day covers it.
Note
Low Risk
Documentation-only change; no product or runtime behavior is modified in this diff.
Overview
Documents that third-party npm packages conflict with protected preview deployments, not only site-wide authentication and personalization.
The third-party libraries page now states that deployments with
packagesindocs.jsonfail when preview deployments require organization login or a password, and adds the reverse rule: while packages are enabled, you cannot turn on authentication, personalization, or preview access restrictions.Reviewed by Cursor Bugbot for commit ee692b2. Bugbot is set up for automated code reviews on this repo. Configure here.