Add changelog entry for split response example selector (Sept 17, 2026) - #6987
Open
fern-api[bot] wants to merge 1 commit into
Open
fern-api[bot] wants to merge 1 commit into
fern-api[bot] wants to merge 1 commit into
Conversation
fern-api
Bot
requested review from
devalog,
jkonrath-postman and
nerminamiller-postman
as code owners
September 17, 2026 00:52
Contributor
|
🌿 Preview your docs: https://fern-preview-2026-09-17-fern-ai-1fb7a4-b90a93be.docs.buildwithfern.com/learn Here are the markdown pages you've updated: |
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.
Created
fern/products/docs/pages/changelog/2026-09-17.mdxwith the new changelog entry documenting the split response example selector UI change. The entry follows the established format — a##heading, a<ChangelogTags>api-reference</ChangelogTags>line, a prose description of the two-dropdown behavior and thename/fallback naming logic, and a<Button>linking to the request/response examples docs page. Nodocs.ymlchange is needed: the changelog section points at the./pages/changelogfolder and automatically picks up every dated.mdxfile placed there.