Repository navigation
feat: publish the versioned site through staging to production - #384
Merged
Merged
Conversation
brendanclement
force-pushed
the
brendan/compose-versioned-site
branch
from
October 22, 2026 20:11
570b2ae to
69c403b
Compare
brendanclement
force-pushed
the
brendan/supervised-publication
branch
from
October 22, 2026 20:11
0f89b81 to
fa15b1b
Compare
brendanclement
marked this pull request as ready for review
October 22, 2026 20:34
brendanclement
force-pushed
the
brendan/supervised-publication
branch
from
October 22, 2026 20:56
fa15b1b to
e25ba00
Compare
brendanclement
force-pushed
the
brendan/compose-versioned-site
branch
2 times, most recently
from
October 22, 2026 23:03
5d2a781 to
4fd461b
Compare
brendanclement
force-pushed
the
brendan/supervised-publication
branch
from
October 22, 2026 23:03
e25ba00 to
138eb81
Compare
rpgreen
approved these changes
Oct 23, 2026
brendanclement
force-pushed
the
brendan/compose-versioned-site
branch
from
October 23, 2026 16:19
4fd461b to
a39f5b8
Compare
brendanclement
force-pushed
the
brendan/supervised-publication
branch
from
October 23, 2026 16:19
138eb81 to
0a50e41
Compare
The Compose workflow checks the saved editions, composes them and records the versioned site as a candidate. Publish puts candidates on staging, keeps staging on main's newest versioned candidate once staging shows the versioned site, and promotes to production only the candidate staging shows after Mintlify reports deploying it, or one production published before, and only if production has not changed since the run was requested.
Production promotes a staging commit only if Mintlify's newest deployment of it, recorded by Mintlify, is live at the staging address in the repository variable MINTLIFY_STAGING_URL. A successful deployment elsewhere, or a status another account added, no longer counts. Staging and production publications share one concurrency group, so no Publish run changes staging between production's check of it and its push. Staging follows main without trusting its own commit message: it is left alone only when its files are main's newest candidate, checked against that run's record, and is published again otherwise.
brendanclement
force-pushed
the
brendan/supervised-publication
branch
from
October 23, 2026 16:24
0a50e41 to
ca54ea2
Compare
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
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.
We can now build the versioned docs site, but we need a way to review it on staging and publish exactly what was reviewed.
This PR connects those steps. Once enabled, merged documentation changes build and publish to staging automatically. Someone can then approve production publication through GitHub. Production receives the same files that were checked on staging, without rebuilding them.
It also handles overlapping updates: publishes run one at a time, older runs can’t overwrite newer ones, and promotion stops if staging has changed since it was requested. Before promoting, it checks that Mintlify has actually deployed the expected staging build.