v2.0.0-beta.3

2.0.0-beta.3 (2026-10-05)

Upgrading from beta.1 or beta.2: portal tabs

The root src/content/nav.json has a new tabs key, and only what it names is a tab (#408). Until now the API reference, SDKs and context plugin were always tabs, and so was every top-level folder named in the root pages. An existing portal changes like this:

• No tabs in the root nav.json, or no root nav.json: the header shows no tab bar, and the API reference, SDKs and context plugin become folders in Home's sidebar. portal generate and portal serve warn about this and print the tabs line to add.
• A folder named in the root pages: it is now a group in Home instead of a tab. To keep it a tab, move it from pages to tabs. A name can't be in both lists.
• Addresses: no page URL changes.

To keep the tabs you had, list them in the order you want, for example:

{
  "tabs": ["guides", "apimatic:sdks", "apimatic:api"],
  "pages": ["index", "..."]
}

Features

• portal: a tabs key in the root nav.json (#408) (9fcf772)

Bug Fixes

• deps: take fumadocs 16.15.17, which links "View as Markdown" under the base path (#413) (137fc7d)
• handle zip service failures (#415) (821a66b)
• portal: default the playground's OAuth client authentication to HTTP Basic (#416) (b99aa87)
• portal: drop the code block guard Fumadocs 12.1 makes unnecessary (#417) (6c2b5df)
• portal: render auth scheme descriptions as Markdown in the playground (#410) (b8ad407)