Skip to content
The Docs Report
Tuesday, November 17, 2026NewsletterRSS

Mintlify Lets Admins Require Review Before Docs Go Live

Mintlify's Nov. 6 changelog adds a publish review gate for Enterprise sites on GitHub, lets Autopilot auto-merge and ends the v1 assistant API Nov. 9.

3 min read

MintlifyEnterprise

Product photo of a white padlock on a cobalt blue, teal and violet gradient

Mintlify admins can now require that editors request a review instead of publishing straight to the deploy branch, according to the company’s Nov. 6 changelog. The setting, called Require review before publishing, is in editor settings. A publisher or admin then approves and publishes the changes. It is available on Enterprise plans for sites on GitHub, and it can’t be turned on while the deploy branch is protected.

Editors get a review gate and partial publishes

Mintlify added a checkbox to each change in the editor’s Publish menu, so an editor can leave some changes out of a publish. The Granular publishing setting is now named Show teammates’ changes, the changelog said.

The dashboard also gained expanded roles on Enterprise plans. Admins can assign publisher and commenter roles, compare roles in a permissions table on the Members page and transfer organization ownership. A Support page lets users open and track support cases. Cases are private by default and can be shared with an organization.

On sites that require review, the admin MCP’s tools can request reviews, list and approve review requests, and publish approved changes, Mintlify said. An AI agent connected through the admin MCP can therefore approve changes.

Breaking changes hit the assistant API, widgets and exports

The v1 assistant message endpoint stops working Nov. 9, according to the changelog. Mintlify tells integrations to move to the v2 endpoint.

Mintlify also removed assistant widget settings from the dashboard. Widgets already embedded keep working on authorized sites, but setting up the widget on a new site now means emailing support@mintlify.com.

Archives from mint export now store assets in _mintlify/assets/ and no longer include index.txt files. Teams that host an export on their own server need to update caching rules, or export with --classic to keep the old layout. mint validate now fails when a page uses an undefined docs.json variable, an unknown component or a missing snippet file. Each of those rules can be switched off with --disable.

Autopilot can merge its own pull requests

Mintlify added an Auto-merge changes switch that lets Autopilot merge its own pull requests for the kinds of work a team reliably merges, the changelog said. Autopilot can also be asked in a chat to run when someone opens, closes, reopens or labels an issue in a connected GitHub repository, or to keep translated pages in sync through a separate pull request.

Work requested directly, in chats on the Autopilot page, Slack, Teams, email replies or pull request comments, no longer costs credits. Automated runs, such as those started by a code merge or a schedule, cost 250 credits when they open a pull request and 250 more each time a later run pushes to it.

Key takeaways

  • Enterprise sites on GitHub can require review before an editor publishes.
  • The v1 assistant message endpoint stops working Nov. 9.
  • mint export archives change layout, and mint validate fails on more problems.
  • Autopilot can auto-merge its own pull requests, and requested work is free.

The take

We think the review gate and auto-merge pull in opposite directions, so a team has to decide which one governs its docs. A review gate says a person signs off before readers see a change. Auto-merge says some changes are safe enough to skip that step. Both can be true, but only if the team names which kinds of change belong to which rule. We’d write that list down before turning on Auto-merge, and check this week that nothing still calls the v1 assistant endpoint.