build(deps): bump the fumadocs group across 1 directory with 4 updates

[dependabot]

Bumps the fumadocs group with 4 updates in the / directory: fumadocs-core, fumadocs-epub, fumadocs-openapi and fumadocs-ui.

Updates fumadocs-core from 16.9.1 to 16.15.4

Release notes

Sourced from fumadocs-core's releases.

fumadocs@16.15.4

• @​fumadocs/base-ui@​16.15.4
• fumadocs-core@16.15.4
• fumadocs-ui@16.15.4

Fix Next.js <Link> not scrolling to top under docs layouts

The page container rendered <main style="display: contents">, which Next.js' scroll handler treats as a hidden element: display: contents generates no box, so its getBoundingClientRect() is all-zero, indistinguishable from display: none. The handler skips it (and the sticky TOC siblings) without ever descending into children, dropping the scroll-to-top on navigation entirely.

The <main> element in Docs, Notebook and Flux page containers is now a real grid item (display: grid; grid-area: main) wrapping the unchanged #nd-page article, which centers via the grid instead of mx-auto. Rendering is identical, but if your custom CSS has element rules on main that were previously inert, they now apply.

fumadocs@16.15.3

• @​fumadocs/base-ui@​16.15.3
• fumadocs-core@16.15.3
• fumadocs-ui@16.15.3

Fix duplicated search result for pages whose description repeats in the content

Pages generated by Fumadocs OpenAPI emit the operation description as both the page description and a content section, so every endpoint page listed the same line twice in the search dialog. Search indexing now skips the page description when an identical content record exists, keeping the record with the heading anchor.

Fix #3509

Remark LLMs: export a component with output: "function"

With output: "function", _markdown becomes a component instead of a string: Markdown content is still stringified at compile time, while JSX elements stay as JSX, receiving their original props.

// fumadocs-mdx collection config
postprocess: {
  includeProcessedMarkdown: { output: 'function' },
},

Render it with renderToMarkdown from fumadocs-core/server. Elements resolve from props.components: a component can call asMarkdown() to output its own Markdown form, other components (including missing ones) are serialized as JSX syntax.

import { renderToMarkdown } from 'fumadocs-core/server';
const { _markdown: Content } = await page.data.load();
const text = await renderToMarkdown(<Content components={getMDXComponents()} />);

getText('processed') keeps working: it renders the component for you, with an optional components map:

const text = await page.data.getText('processed', { components: getMDXComponents() });

Supported in bundler collections with both compilers, and in dynamic: true collections & @fumadocs/satteri/local-md with the Sätteri compiler.

... (truncated)

Commits

• 7d6fb97 Merge pull request #3516 from fuma-nama/tegami/version-packages
• 2d4706f chore: bump deps
• e616cb3 fix(ui): improve solar theme on new \<main> container
• 19442a3 feat(openapi): support 3.2 tag group
• a9054b3 fix(openapi): also upgrade the external documents
• dbf0f12 fix(ui): Next.js auto-scroll bug
• 5cd7b69 Merge pull request #3510 from fuma-nama/tegami/version-packages
• 814559b docs: introduce React Markdown Components
• b4d689d refactor(core(: rename options
• eefd3e0 feat(satteri): show the type table as a table in markdown form
• Additional commits viewable in compare view

Updates fumadocs-epub from 1.1.0 to 1.2.0

Commits

• 9a26903 Version Packages
• 3e33f43 perf(satteri): reduce clones
• 3597c9d perf(satteri): persist results
• 0f389cf feat(satteri): decouple imports/exports from compile()
• 4611f97 feat(satteri): full rehype-toc functionality
• d095300 fix(satteri): workaround common issues
• 0297e25 configure pretrust
• 02c242b chore(satteri): clean code
• 3d80b8b fix(mdx): ensure satteri integration is optional
• 0ec19af feat(satteri): more tests & move remark-include
• Additional commits viewable in compare view

Updates fumadocs-openapi from 10.9.0 to 11.3.5

Release notes

Sourced from fumadocs-openapi's releases.

fumadocs-openapi@11.3.5

Fix OpenAPI 3.0 example in external files crashing OpenAPIPage

The version upgrader ran after external documents were embedded under x-ext, where it can no longer classify schemas by their JSON path: a schema-level example from an external 3.0 file became an Example Object map instead of the JSON Schema examples array, crashing the schema UI with schema.examples is not iterable.

Each document is now upgraded before bundling embeds it. This also honors the external file's own declared OpenAPI version, so a 3.0 file referenced from a 3.1 document is upgraded too (previously it was skipped entirely).

Support OpenAPI 3.2 tag hierarchy in groupBy: 'tag'

generateFiles now follows the tag hierarchy introduced in OpenAPI 3.2: a tag with a parent becomes a folder nested inside its parent tag's folder (including the generated meta.json), and tags with a kind other than nav no longer form groups, matching their intent (e.g. badge).

Operations referencing undeclared tags or having no tags are no longer dropped silently, which previously could produce an empty output directory. Undeclared tags now form their own group, and untagged operations are grouped under an unknown folder with a warning.

fumadocs-openapi@11.3.4

Support HTTP Basic client authentication in OAuth password flow

Some OAuth servers require client credentials in an HTTP Basic Authorization header instead of the request body. The password flow dialog now offers a Client Authentication select to choose between the two methods, as described in RFC 6749, section 2.3.1.

Fix #3506

fumadocs-openapi@11.3.3

Fix playground result URL

fumadocs-openapi@11.3.2

Improve OAuth Password Flow

Support optional Client ID and Client Secret in the OAuth password flow of API playground, they are sent along the token request when specified.

Enhance result display of API playground

The response panel now gives you the full picture of a request:

• the resolved request URL, including path and query parameters
• response headers in a collapsible list
• response body labeled with its content type

Client-side errors also show the request URL, making issues like a wrong server URL easy to spot.

For custom ResultDisplay components, FetchResult now carries a url field.

@fumadocs/language includes translations for the new UI.

fumadocs-openapi@11.3.1

Simplify cache

fumadocs-openapi@11.3.0

Redesign source API

Content sources can hook into the static loader they are attached to, and dynamic sources can opt out of the loader's in-memory file cache.

... (truncated)

Commits

• See full diff in compare view

Updates fumadocs-ui from 16.9.1 to 16.15.4

Release notes

Sourced from fumadocs-ui's releases.

fumadocs@16.15.4

• @​fumadocs/base-ui@​16.15.4
• fumadocs-core@16.15.4
• fumadocs-ui@16.15.4

Fix Next.js <Link> not scrolling to top under docs layouts

The page container rendered <main style="display: contents">, which Next.js' scroll handler treats as a hidden element: display: contents generates no box, so its getBoundingClientRect() is all-zero, indistinguishable from display: none. The handler skips it (and the sticky TOC siblings) without ever descending into children, dropping the scroll-to-top on navigation entirely.

The <main> element in Docs, Notebook and Flux page containers is now a real grid item (display: grid; grid-area: main) wrapping the unchanged #nd-page article, which centers via the grid instead of mx-auto. Rendering is identical, but if your custom CSS has element rules on main that were previously inert, they now apply.

fumadocs@16.15.3

• @​fumadocs/base-ui@​16.15.3
• fumadocs-core@16.15.3
• fumadocs-ui@16.15.3

Fix duplicated search result for pages whose description repeats in the content

Pages generated by Fumadocs OpenAPI emit the operation description as both the page description and a content section, so every endpoint page listed the same line twice in the search dialog. Search indexing now skips the page description when an identical content record exists, keeping the record with the heading anchor.

Fix #3509

Remark LLMs: export a component with output: "function"

With output: "function", _markdown becomes a component instead of a string: Markdown content is still stringified at compile time, while JSX elements stay as JSX, receiving their original props.

// fumadocs-mdx collection config
postprocess: {
  includeProcessedMarkdown: { output: 'function' },
},

Render it with renderToMarkdown from fumadocs-core/server. Elements resolve from props.components: a component can call asMarkdown() to output its own Markdown form, other components (including missing ones) are serialized as JSX syntax.

import { renderToMarkdown } from 'fumadocs-core/server';
const { _markdown: Content } = await page.data.load();
const text = await renderToMarkdown(<Content components={getMDXComponents()} />);

getText('processed') keeps working: it renders the component for you, with an optional components map:

const text = await page.data.getText('processed', { components: getMDXComponents() });

Supported in bundler collections with both compilers, and in dynamic: true collections & @fumadocs/satteri/local-md with the Sätteri compiler.

... (truncated)

Commits

• 7d6fb97 Merge pull request #3516 from fuma-nama/tegami/version-packages
• 2d4706f chore: bump deps
• e616cb3 fix(ui): improve solar theme on new \<main> container
• 19442a3 feat(openapi): support 3.2 tag group
• a9054b3 fix(openapi): also upgrade the external documents
• dbf0f12 fix(ui): Next.js auto-scroll bug
• 5cd7b69 Merge pull request #3510 from fuma-nama/tegami/version-packages
• 814559b docs: introduce React Markdown Components
• b4d689d refactor(core(: rename options
• eefd3e0 feat(satteri): show the type table as a table in markdown form
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
coven-docs	Error		Aug 31, 2026 1:21pm