Changelog

Logo right-text property

You can now display custom text to the right of your logo image using the new right-text property in your logo configuration. This is useful for adding labels like “Docs” or “API” next to your logo.

1
logo:
2
  dark: assets/images/logo-dark.svg
3
  light: assets/images/logo-light.svg
4
  right-text: Docs

Learn more about the logo configuration options.

Schema snippet component

The new <SchemaSnippet> component displays type definitions from your API Reference as a JSON code block. Use it alongside the <Schema> component to show both a JSON representation and the detailed field breakdown of your data models.

1
{
2
  "model": "claude-3.5",
3
  "system-prompt": "string"
4
}

1
<SchemaSnippet type="AIChatConfig" title="The AIChatConfig Object" />

Learn more about the Schema snippet component.

Last updated frontmatter property

You can now display a “Last updated” message in the page footer using the new last-updated frontmatter property. This helps readers know when the content was last modified.

1
---
2
title: API Reference
3
last-updated: December 9, 2025
4
---

The date is displayed as-is in small text below the on-page feedback, so you can use any date format you prefer.

Learn more about the last-updated frontmatter property.

Footer component for API Reference descriptions

You can now use the <Footer> component in your API endpoint descriptions to add content that renders at the bottom of the page, below the response section. This is useful for related links, additional context, or notes that make more sense at the end of the endpoint documentation.

1
paths:
2
  /plants:
3
    get:
4
      summary: List all plants
5
      description: |
6
        Get a list of all plants in the system.
7
8
        <Footer>
9
        ## Related endpoints
10
11
        - [Create a plant](/api-reference/plants/create)
12
        - [Update a plant](/api-reference/plants/update)
13
        </Footer>

Learn more about adding footers and other Markdown content to your API Reference.

Security update: React Server Components vulnerability patched

We’ve updated our platform to address a critical security vulnerability (CVE-2025-66478) in React Server Components. This vulnerability, rated CVSS 10.0, could allow remote code execution when processing attacker-controlled requests in unpatched environments.

The vulnerability originates in the upstream React implementation (CVE-2025-55182) and affects Next.js applications using the App Router with React Server Components.

What we did

We upgraded our platform dependencies to the patched versions:

• Next.js: Updated from 15.5.4 to 15.5.7
• React: Updated from 19.0.0 to 19.0.1
• React-DOM: Updated from 19.0.0 to 19.0.1

These versions include the hardened React Server Components implementation that resolves the vulnerability.

Impact on Fern users

No action is required from Fern Docs users. The security patch has been applied to all Fern-hosted documentation sites automatically.

For self-hosted deployments, we recommend updating to the latest Fern platform version to ensure you have the security fix.

References

• Next.js Security Advisory: CVE-2025-66478
• Next.js 15.5.7 Release
• React 19.0.1 Release

Tag description pages for API references

You can now use OpenAPI tag descriptions as summary pages for API reference sections. When you set tag-description-pages: true in your API reference configuration, Fern automatically creates a summary page for each tag using its description from your OpenAPI specification.

1
navigation:
2
  - api: API Reference
3
    tag-description-pages: true

Learn more about API reference configuration options.

Product and version-specific announcement banners

Announcement banners can now be configured at multiple levels to target specific products or versions.

The override hierarchy is:

1. Version-level - Highest priority, always shown when defined for a specific version
2. Product-level - Used when no version-level announcement exists for a product
3. Config-level - Fallback announcement shown across all products/versions when no specific override is defined

Add the announcement property directly to items in the products: or versions: lists in your docs.yml file:

1
# Config-level announcement (fallback)
2
announcement:
3
  message: "Welcome to our documentation!"
4
5
products:
6
  - display-name: Docs
7
    path: ./products/docs/docs.yml
8
    # Product-level announcement
9
    announcement:
10
      message: "Docs product is in beta."
11
12
    versions:
13
      - display-name: v1
14
        path: ./products/docs/v1/docs.yml
15
        # Version-level announcement (highest priority)
16
        announcement:
17
          message: "v1 is in maintenance mode. Upgrade to v2."

Learn more about configuring announcement banners.

LLM content visibility tags

New <llms-only> and <llms-ignore> tags let you provide additional context for AI assistants while keeping your documentation site (for human readers) clean and focused.

Use <llms-only> to show content exclusively to AI assistants via LLM endpoints (like /llms.txt) while hiding it from your documentation site:

1
<llms-only>
2
  This technical context is only visible to AI assistants via LLM endpoints.
3
</llms-only>

Use <llms-ignore> to show content only on your documentation site while excluding it from LLM endpoints:

1
<llms-ignore>
2
  <Callout intent="info">
3
    This callout appears on your documentation site but not in LLM endpoints.
4
  </Callout>
5
</llms-ignore>

Learn more about controlling content visibility for humans and agents.

Link target property

Control where links open with the target property. Available for product, tab, navbar, and page links. For typical documentation sites, links can open in the same tab (_self) or new tab (_blank). For documentation embedded in a dashboard or iframe, links can open in the parent frame (_parent) or topmost frame (_top).

1
navigation:
2
  - section: Home
3
    contents:
4
      - page: Introduction
5
        path: ./intro.mdx
6
      - link: Our YouTube channel
7
        href: https://www.youtube.com/
8
        target: _blank

Learn more about links and other navigational elements.

Multiple authentication schemes in the API Explorer

The API Explorer now supports multiple authentication schemes and combinations of authentication schemes for OpenAPI specs.

First, configure your OpenAPI spec with multiple security options:

1
/plant/search/status:
2
  get:
3
    tags:
4
      - plant
5
    summary: Search plants by status
6
    description: Filter plants based on their current status.
7
    operationId: searchPlantsByStatus
8
    security:
9
      - bearerAuth: []  # Option 1: Bearer token only (OR)
10
      - basicAuth: []   # Option 2: Basic auth AND API key (combined)
11
        apiKey: []

Then, the API Explorer automatically displays all available authentication options in a dropdown menu, allowing users to select and configure their preferred authentication method before sending requests.

Learn more about configuring authentication in the API Explorer documentation.

Files component for displaying file tree structures

The new <Files> component creates visual file tree structures with expandable folders and nested files. Use it to show project structures, directory layouts, or any hierarchical file organization in your documentation.

The component consists of three parts: <Files> as the container, <Folder> for directories that can be expanded or collapsed, and <File> for individual files. Folders and files support optional href properties to make them clickable links, and folders can use defaultOpen to start expanded when the page loads.

1
<Files>
2
  <Folder name="components" highlighted defaultOpen>
3
    <File name="accordion.mdx" />
4
    <File name="button.mdx" />
5
    <File name="card.mdx" />
6
    <File name="tabs.mdx" />
7
  </Folder>
8
  <Folder name="assets">
9
    <File name="styles.css" />
10
  </Folder>
11
  <File name="markdown.mdx" href="/learn/docs/writing-content/markdown" />
12
  <File name="README.md" comment="Contribute to the docs"/>
13
  <File name="markdown.mdx" href="/learn/docs/writing-content/markdown-basics" />
14
  <File name="README.md" />
15
</Files>

Read more in the Files component documentation.