Skip to content

chore(deps): bump the npm-minor-patch group in /docs/site with 6 updates - #8

Merged
yo61-lastlight[bot] merged 1 commit into
mainfrom
dependabot/npm_and_yarn/docs/site/npm-minor-patch-f9a158a959
Sep 2, 2026
Merged

chore(deps): bump the npm-minor-patch group in /docs/site with 6 updates#8
yo61-lastlight[bot] merged 1 commit into
mainfrom
dependabot/npm_and_yarn/docs/site/npm-minor-patch-f9a158a959

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 1, 2026

Copy link
Copy Markdown
Contributor

Bumps the npm-minor-patch group in /docs/site with 6 updates:

Package From To
fumadocs-core 16.15.1 16.15.4
fumadocs-mdx 15.3.1 15.4.0
fumadocs-ui 16.15.1 16.15.4
lucide-react 1.34.0 1.38.0
next 16.3.2 16.3.4
@types/node 26.3.0 26.4.0

Updates fumadocs-core from 16.15.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-mdx from 15.3.1 to 15.4.0

Release notes

Sourced from fumadocs-mdx's releases.

fumadocs-mdx@15.4.0

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.

Commits
  • 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
  • 49afb7d docs: support .md apart from .mdx suffix
  • 399bea9 feat(mdx,satteri): support dynamic markdown renderer on remark-llms plugin
  • 7eef0d8 feat(core): React Markdown Component
  • 3d07ef5 fix(core): duplicated record when indexing
  • 0687a8b Version Packages (#3507)
  • cc53d34 internal(core): drop negotiator
  • Additional commits viewable in compare view

Updates fumadocs-ui from 16.15.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

Updates lucide-react from 1.34.0 to 1.38.0

Release notes

Sourced from lucide-react's releases.

Version 1.38.0

What's Changed

Full Changelog: lucide-icons/lucide@1.36.0...1.38.0

Version 1.37.0

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@1.35.0...1.37.0

Version 1.36.0

What's Changed

... (truncated)

Commits

Updates next from 16.3.2 to 16.3.4

Release notes

Sourced from next's releases.

v16.3.4

Follow-up release to v16.3.3 re-enabling AVIF Image Optimization (#97949).

The following bug fixes have been backported. It does not include all pending features/changes on canary.

  • testmode: Fix infinite recursion in testmode passthrough fetch (#97691)
  • Fix build error when aliasing typescript to @​typescript/typescript6 (#97997)
  • Fix unset crossOrigin in Turbopack manifests (#97930)

Credits

Huge thanks to @​eps1lon, @​mischnic, and @​timneutkens for helping!

v16.3.3

This release contains security fixes for the following advisories:

Critical:

Commits
  • 299180d v16.3.4
  • 12e173d [16.3.x] Re-enable AVIF image optimization and require sharp 0.35.4 (#97949)
  • 5d9022e [backport] Fix unset crossOrigin in Turbopack manifests (#97930)
  • d8f4560 [16.3.x] Fix build error when aliasing typescript to @​typescript/typescript6 ...
  • 656aebf [16.3] testmode: Fix infinite recursion in testmode passthrough fetch (#97691)
  • f37c1d6 [16.3.x] ci: remove pull_request_stats workflow (#97975)
  • a9a1cb7 v16.3.3
  • 968b9fc [16.3.x] Fix ISR misses with backslashes in segments when deployed on Windows
  • 3a15b4a [16.3.x] [next/image]: disable avif image optimization
  • 7378b51 Backport/docs fixes 16.3 (#97649)
  • Additional commits viewable in compare view

Updates @types/node from 26.3.0 to 26.4.0

Commits

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

@dependabot
chore(deps): bump the npm-minor-patch group in /docs/site with 6 updates
8be0c00 
Bumps the npm-minor-patch group in /docs/site with 6 updates:

| Package | From | To |
| --- | --- | --- |
| [fumadocs-core](https://github.com/fuma-nama/fumadocs) | `16.15.1` | `16.15.4` |
| [fumadocs-mdx](https://github.com/fuma-nama/fumadocs) | `15.3.1` | `15.4.0` |
| [fumadocs-ui](https://github.com/fuma-nama/fumadocs) | `16.15.1` | `16.15.4` |
| [lucide-react](https://github.com/lucide-icons/lucide/tree/HEAD/packages/lucide-react) | `1.34.0` | `1.38.0` |
| [next](https://github.com/vercel/next.js) | `16.3.2` | `16.3.4` |
| [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) | `26.3.0` | `26.4.0` |


Updates `fumadocs-core` from 16.15.1 to 16.15.4
- [Release notes](https://github.com/fuma-nama/fumadocs/releases)
- [Commits](https://github.com/fuma-nama/fumadocs/compare/fumadocs@16.15.1...fumadocs@16.15.4)

Updates `fumadocs-mdx` from 15.3.1 to 15.4.0
- [Release notes](https://github.com/fuma-nama/fumadocs/releases)
- [Commits](https://github.com/fuma-nama/fumadocs/compare/fumadocs-mdx@15.3.1...fumadocs-mdx@15.4.0)

Updates `fumadocs-ui` from 16.15.1 to 16.15.4
- [Release notes](https://github.com/fuma-nama/fumadocs/releases)
- [Commits](https://github.com/fuma-nama/fumadocs/compare/fumadocs@16.15.1...fumadocs@16.15.4)

Updates `lucide-react` from 1.34.0 to 1.38.0
- [Release notes](https://github.com/lucide-icons/lucide/releases)
- [Commits](https://github.com/lucide-icons/lucide/commits/1.38.0/packages/lucide-react)

Updates `next` from 16.3.2 to 16.3.4
- [Release notes](https://github.com/vercel/next.js/releases)
- [Commits](vercel/next.js@v16.3.2...v16.3.4)

Updates `@types/node` from 26.3.0 to 26.4.0
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node)

---
updated-dependencies:
- dependency-name: fumadocs-core
  dependency-version: 16.15.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: npm-minor-patch
- dependency-name: fumadocs-mdx
  dependency-version: 15.4.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: npm-minor-patch
- dependency-name: fumadocs-ui
  dependency-version: 16.15.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: npm-minor-patch
- dependency-name: lucide-react
  dependency-version: 1.38.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: npm-minor-patch
- dependency-name: next
  dependency-version: 16.3.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: npm-minor-patch
- dependency-name: "@types/node"
  dependency-version: 26.4.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-minor-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Sep 1, 2026
@yo61-lastlight yo61-lastlight Bot added the dependency-trivial Trivial & safe dependency update (auto-merge path). label Sep 1, 2026
@yo61-lastlight
yo61-lastlight Bot enabled auto-merge (squash) September 1, 2026 23:01
@yo61-lastlight

yo61-lastlight Bot commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

This dependency update looks safe to land: it only changes dependency versions in docs/site/package.json plus the generated pnpm-lock.yaml, and the settled checks are green. Auto-merge is armed, but the PR is currently blocked with no approving review, so a maintainer needs to approve or merge it.

@yo61-lastlight yo61-lastlight Bot added the requires-human Last Light can't proceed automatically; a maintainer must handle it. label Sep 1, 2026
@yo61-lastlight
yo61-lastlight Bot merged commit 0caaaa2 into main Sep 2, 2026
11 checks passed
@yo61-lastlight
yo61-lastlight Bot deleted the dependabot/npm_and_yarn/docs/site/npm-minor-patch-f9a158a959 branch September 2, 2026 11:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@robinbowes robinbowes robinbowes approved these changes

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file dependency-trivial Trivial & safe dependency update (auto-merge path). javascript Pull requests that update javascript code requires-human Last Light can't proceed automatically; a maintainer must handle it.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@robinbowes