* docs: add September 4, 2026 changelog entry
* docs: translate September 4, 2026 changelog entry into es, fr, zh
* docs: correct and expand the September 4, 2026 changelog entry
Verified the entry against merged code in mintlify/server and mintlify/mint
for Aug 28 - Sep 4, plus #shipped and the #proj- channels.
Added:
- Bring your own model (server#7806, mint#10517/#10538, announced in #shipped
Aug 28). Documented at ai/bring-your-own-model.mdx since Aug 28 but never
announced in any changelog entry.
- Notification preferences (server#7792/#7793/#7815, flag removed in #7867 and
mint#10613, announced in #shipped Aug 30).
- Media on private pages (server#7828/#7837/#7846/#7891, mint#10532/#10564/#10578).
Corrected:
- Automation failure emails are opt-in. server#7811 defaults automation run
notifications to off; the entry presented them as automatic.
- The translations fix (server#7872) changes the translation prompt, so it
applies to newly translated content rather than all translated pages.
- Optional field toggles (mint#10522) landed in the playground modal only.
Removed two "See" links that resolved to pages not yet documenting the feature
(/editor/publish for selective publish, /analytics for the page filter), and
repointed collaborative source mode at /editor/collaborate#real-time-editing.
Dropped the es/fr/zh blocks so the post-merge translation automation
regenerates them from the corrected English.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* copyedit
---------
Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-authored-by: Ethan Palm <56270045+ethanpalm@users.noreply.github.com>
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
* Remove Stainless integration page and fix Speakeasy config examples
Stainless was acquired by Anthropic (announced 2026-05-18) and wound down
all hosted products, including the SDK generator: "new signups, projects,
and SDKs will not be available." The integration page documented a
hosted-platform flow (Studio -> Release tab -> Setup OpenAPI publishing)
that no new reader can complete, so it is removed and redirected to the
vendor-neutral x-codeSamples page.
Speakeasy is still operating and the integration still works, but its
docs.json examples used the pre-docs.json schema (top-level "anchors"/
"tabs" keyed on "name"/"url"). Updated to the current navigation.anchors
/ navigation.tabs shape so the snippets are copy-pasteable.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* Collapse Speakeasy page into the Add SDK examples page
With Stainless removed, the Integrations > SDKs group held a single page.
Fold the Speakeasy setup steps into api-playground/adding-sdk-examples.mdx
as a "Generate examples with Speakeasy" section and drop the group.
The page now covers both routes to x-codeSamples: writing samples by hand
and pulling autogenerated ones from a Speakeasy combined spec. Old page
paths redirect to the new section anchor.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* Apply batched suggestions from code review
Co-authored-by: Ethan Palm <56270045+ethanpalm@users.noreply.github.com>
* use steps
---------
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
* docs: close reader-question gaps in automations, go-live, and Osano pages
Reworks the English-only subset of #6954 after review.
- automations/create.mdx: replace the redundant "review the output" tip
with a "Test your automation" section. Drops #6954's advice to test
before relying on "a schedule or event"; per /automations/manage most
automations can run manually only with a schedule trigger. Links the
run history section rather than the raw dashboard URL so credit usage
and run statuses stay documented in one place.
- migration-services/go-live-checklist.mdx: add the preview-URL and
mint broken-links steps to the existing Content validation section
instead of a new section. #6954's auth and page-access bullets
duplicated the Security section, and its redirects bullet is folded
into the existing one.
- integrations/privacy/osano.mdx: add a Verify the banner section and
note that content-directory .js files need no docs.json entry.
Excludes #6954's editor/tutorial.mdx prerequisites: the Editor group
root already documents editor access and roles, and the connected-repo
bullet is wrong for projects that skipped Git setup during onboarding.
The network-access.mdx lockout section is held pending confirmation of
what support can do for a locked-out org. Translations omitted; they
are generated after merge.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* Apply batched suggestions from code review
Co-authored-by: Ethan Palm <56270045+ethanpalm@users.noreply.github.com>
---------
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
* Document x-mint playground expandSections setting
Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
* Apply review suggestion to expandSections wording
Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
* Update expandSections docs for nested object field behavior
Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
* Clarify that the top-level body object stays expanded
Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
* Rename playground setting to expand
Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
---------
Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
* docs: document web editor branch list visibility rule and workarounds
* docs: add fr/es/zh translations for branch visibility updates
* docs: correct editor branch list rule and scope the URL workaround
The visibility rule as first written covered only branches pushed
directly to a Git provider. Verified against the editor branch code:
records are also soft-deleted when a pull request is merged or closed
(editorBranch.service.ts), the list defaults to PR states none/draft/open
(editorBranch.validators.ts), and cross-repository (fork) pull requests
are filtered out. Those cases match the support threads about branches
disappearing after publishing, so document them.
Also scope the URL workaround: without an editor branch record,
autocommit is skipped, the branch diff fails, and rename/delete return
404. It is a view-and-edit fallback, not an equivalent to opening a
pull request.
Drop the hand-written es/fr/zh pages and locale nav entries; those are
generated after merge.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* Apply suggestion from @ethanpalm
---------
Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-authored-by: Ethan Palm <56270045+ethanpalm@users.noreply.github.com>
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
* docs: fix quality gaps in recently changed pages
* docs: mirror PR changes into es, fr, zh translations
* docs: address review feedback on quality-check fixes
- route53-cloudfront: split the Route 53 section into "Add your domain to
the distribution" and "Create the Route 53 record", give the alternate
domain name / ACM step numbered steps and the console path, and warn
that CloudFront only accepts certificates issued in us-east-1
- cli/commands: drop the intro sentence that restated the frontmatter
description; match the link text to the target page title
- poc-onboarding: stop coupling DNS setup to authentication in the
participants table, since auth works on .mintlify.site
- editor/pages: note that "Move to trash" has no trash view to restore
from, and that recovery after publishing is through the repository
Mirrored into es, fr, and zh.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* Update pages.mdx
---------
Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-authored-by: Ethan Palm <56270045+ethanpalm@users.noreply.github.com>
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Ports two details from the superseded bot PR #7134 into the dedicated
bring your own model page:
- The OpenAI-compatible base URL must use HTTPS and point to a publicly
reachable host.
- The AI model section only appears in the dashboard when the contract
includes the add-on, so readers who can't find it know why.
Also adds a cross-link from the assistant configuration page, which had
no path to the bring your own model page. Placed in Manage billing next
to the existing credits link rather than as its own section, since the
configuration covers the agent and automations too, not just the
assistant.
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>