Skip to content

chore(deps): bump the npm-minor-patch group across 2 directories with 6 updates - #170

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/npm-minor-patch-a18a6ef387
Open

chore(deps): bump the npm-minor-patch group across 2 directories with 6 updates#170
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/npm-minor-patch-a18a6ef387

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 8, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

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

Package From To
next 16.2.11 16.3.3
@types/react 19.2.17 19.2.18
@types/react-dom 19.2.3 19.2.5
cnfast 0.0.8 0.1.0
fumadocs-core 16.10.7 16.15.4
fumadocs-mdx 15.0.13 15.4.0

Bumps the npm-minor-patch group with 4 updates in the /apps/docs directory: next, cnfast, fumadocs-core and fumadocs-mdx.

Updates next from 16.2.11 to 16.3.3

Release notes

Sourced from next's releases.

v16.3.3

This release contains security fixes for the following advisories:

Critical:

v16.3.2

[!NOTE] This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

  • [backport] Scope app-entry export validation to files inside the app directory (#97357)
  • [backport] Fix catch-all index page being served for every other slug (#97416)
  • [16.3] Turbopack: don't trace embedded WASM loader helpers (#97353) (#97463)
  • [16.3] Turbopack: retain conditions when replacing resolve request keys (#97453)
  • [16.3.x] Fix Turbopack worker chunk loading with asset prefix (#97419)
  • [16.3.x] Authenticate Turborepo remote caching with OIDC instead of a static PAT (#97603)

Credits

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

v16.3.1

What's Changed

Full Changelog: vercel/next.js@v16.3.0...v16.3.1

... (truncated)

Commits
  • 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)
  • 528c1cd [16.3.x] Stop generating error codes (#97780)
  • d0ac882 v16.3.2
  • 81deb92 [16.3.x] Authenticate Turborepo remote caching with OIDC instead of a static ...
  • cd714d9 [16.3.x] Fix Turbopack worker chunk loading with asset prefix (#97419)
  • 5ac2327 [16.3] Turbopack: retain conditions when replacing resolve request keys (#97453)
  • 0ccb3e7 [16.3] Turbopack: don't trace embedded WASM loader helpers (#97353) (#97463)
  • Additional commits viewable in compare view

Updates @types/react from 19.2.17 to 19.2.18

Commits

Updates @types/react-dom from 19.2.3 to 19.2.5

Commits

Updates cnfast from 0.0.8 to 0.1.0

Changelog

Sourced from cnfast's changelog.

0.1.0

Minor Changes

  • 8643c3c: Add createCn for custom tailwind-merge configuration.

    createCn(config) builds a cn that honors a custom merge config, accepting the same { override, extend } shape as tailwind-merge's extendTailwindMerge (or a (defaultConfig) => config function). The default cn export is unchanged. Also re-exports createTailwindMerge, getDefaultConfig, and mergeConfigs. Fixes custom font-size/class-group configs being ignored (#6).

Patch Changes

  • fix
Commits

Updates fumadocs-core from 16.10.7 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.0.13 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.

fumadocs-mdx@15.3.1

Scope lastModified git log to the content directory

git log is scoped to the collection's content directory instead of buffering the repository's entire history in every worker.

Fix Vite dev server crash on declaration-only dependencies

The injected Vite config no longer pre-bundles packages without runtime JavaScript, such as @types/mdx. Pre-bundling them made esbuild parse .d.ts files and fail on imports that only exist in type space, crashing the dev server.

Encode import.meta.glob query values

The Vite codegen passed the query to import.meta.glob as an object, letting the bundler serialize it. Rolldown inlines the values as-is, so a macro id such as src/lib/source.ts#docs left an unescaped / in the content file's module id and relative imports from that module (e.g. images from ![Banner](https://github.com/fuma-nama/fumadocs/blob/HEAD/logo.png)) failed to resolve, since the importer's directory is derived from the raw id.

The query is now serialized (and percent-encoded) by Fumadocs itself, matching what the Node.js codegen already did.

fumadocs-mdx@15.3.0

Sätteri 0.10

@fumadocs/satteri now requires satteri ^0.10.3, and the plugins were rewritten on its new capabilities:

  • Exports (frontmatter, toc, structuredData, …) are emitted by an after document hook instead of an anchor marker appended to the source, so plugins no longer see (or need to skip) the anchor node.

... (truncated)

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-core from 16.10.7 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.0.13 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.

fumadocs-mdx@15.3.1

Scope lastModified git log to the content directory

git log is scoped to the collection's content directory instead of buffering the repository's entire history in every worker.

Fix Vite dev server crash on declaration-only dependencies

The injected Vite config no longer pre-bundles packages without runtime JavaScript, such as @types/mdx. Pre-bundling them made esbuild parse .d.ts files and fail on imports that only exist in type space, crashing the dev server.

Encode import.meta.glob query values

The Vite codegen passed the query to import.meta.glob as an object, letting the bundler serialize it. Rolldown inlines the values as-is, so a macro id such as src/lib/source.ts#docs left an unescaped / in the content file's module id and relative imports from that module (e.g. images from ![Banner](https://github.com/fuma-nama/fumadocs/blob/HEAD/logo.png)) failed to resolve, since the importer's directory is derived from the raw id.

The query is now serialized (and percent-encoded) by Fumadocs itself, matching what the Node.js codegen already did.

fumadocs-mdx@15.3.0

Sätteri 0.10

@fumadocs/satteri now requires satteri ^0.10.3, and the plugins were rewritten on its new capabilities:

  • Exports (frontmatter, toc, structuredData, …) are emitted by an after document hook instead of an anchor marker appended to the source, so plugins no longer see (or need to skip) the anchor node.

... (truncated)

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 next from 16.2.11 to 16.3.3

Release notes

Sourced from next's releases.

v16.3.3

This release contains security fixes for the following advisories:

Critical:

v16.3.2

[!NOTE] This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

  • [backport] Scope app-entry export validation to files inside the app directory (#97357)
  • [backport] Fix catch-all index page being served for every other slug (#97416)
  • [16.3] Turbopack: don't trace embedded WASM loader helpers (#97353) (#97463)
  • [16.3] Turbopack: retain conditions when replacing resolve request keys (#97453)
  • [16.3.x] Fix Turbopack worker chunk loading with asset prefix (#97419)
  • [16.3.x] Authenticate Turborepo remote caching with OIDC instead of a static PAT (#97603)

Credits

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

v16.3.1

What's Changed

Full Changelog: vercel/next.js@v16.3.0...v16.3.1

... (truncated)

Commits
  • 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)
  • 528c1cd [16.3.x] Stop generating error codes (#97780)
  • d0ac882 v16.3.2
  • 81deb92 [16.3.x] Authenticate Turborepo remote caching with OIDC instead of a static ...
  • cd714d9 [16.3.x] Fix Turbopack worker chunk loading with asset prefix (#97419)
  • 5ac2327 [16.3] Turbopack: retain conditions when replacing resolve request keys (#97453)
  • 0ccb3e7 [16.3] Turbopack: don't trace embedded WASM loader helpers (#97353) (#97463)
  • Additional commits viewable in compare view

Updates @types/react from 19.2.17 to 19.2.18

Commits

Updates @types/react-dom from 19.2.3 to 19.2.5

Commits

Updates next from 16.2.11 to 16.3.3

Release notes

Sourced from next's releases.

v16.3.3

This release contains security fixes for the following advisories:

Critical:

v16.3.2

[!NOTE] This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

  • [backport] Scope app-entry export validation to files inside the app directory (#97357)
  • [backport] Fix catch-all index page being served for every other slug (#97416)
  • [16.3] Turbopack: don't trace embedded WASM loader helpers (#97353) (#97463)
  • [16.3] Turbopack: retain conditions when replacing resolve request keys (#97453)
  • [16.3.x] Fix Turbopack worker chunk loading with asset prefix (#97419)
  • [16.3.x] Authenticate Turborepo remote caching with OIDC instead of a static PAT (#97603)

Credits

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

v16.3.1

What's Changed

Full Changelog: vercel/next.js@v16.3.0...v16.3.1

... (truncated)

Commits
  • 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)
  • 528c1cd [16.3.x] Stop generating error codes (#97780)
  • d0ac882 v16.3.2
  • 81deb92 [16.3.x] Authenticate Turborepo remote caching with OIDC instead of a static ...
  • cd714d9 [16.3.x] Fix Turbopack worker chunk loading with asset prefix (#97419)
  • 5ac2327 [16.3] Turbopack: retain conditions when replacing resolve request keys (#97453)
  • 0ccb3e7 [16.3] Turbopack: don't trace embedded WASM loader helpers (#97353) (#97463)
  • Additional commits viewable in compare view

Updates cnfast from 0.0.8 to 0.1.0

Changelog

Sourced from cnfast's changelog.

0.1.0

Minor Changes

  • 8643c3c: Add createCn for custom tailwind-merge configuration.

    createCn(config) builds a cn that honors a custom merge config, accepting the same { override, extend } shape as tailwind-merge's extendTailwindMerge (or a (defaultConfig) => config function). The default cn export is unchanged. Also re-exports createTailwindMerge, getDefaultConfig, and mergeConfigs. Fixes custom font-size/class-group configs being ignored (#6).

Patch Changes

  • fix
Commits

Updates fumadocs-core from 16.10.7 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.0.13 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.

fumadocs-mdx@15.3.1

Scope lastModified git log to the content directory

git log is scoped to the collection's content directory instead of buffering the repository's entire history in every worker.

Fix Vite dev server crash on declaration-only dependencies

The injected Vite config no longer pre-bundles packages without runtime JavaScript, such as @types/mdx. Pre-bundling them made esbuild parse .d.ts files and fail on imports that only exist in type space, crashing the dev server.

Encode import.meta.glob query values

The Vite codegen passed the query to import.meta.glob as an object, letting the bundler serialize it. Rolldown inlines the values as-is, so a macro id such as src/lib/source.ts#docs left an unescaped /<...

Description has been truncated

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Aug 8, 2026
@openooxml-bot

openooxml-bot Bot commented Aug 8, 2026

Copy link
Copy Markdown
Contributor

All contributors have signed the CLA — thank you! ✍️ ✅

Posted by the CLA bot.

@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/npm-minor-patch-a18a6ef387 branch 2 times, most recently from 0dd231e to 79a443d Compare August 15, 2026 00:34
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/npm-minor-patch-a18a6ef387 branch 2 times, most recently from 3134d50 to 30c1241 Compare August 29, 2026 00:34
@dependabot
chore(deps): bump the npm-minor-patch group across 2 directories with…
6cb8bfa 
… 6 updates

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

| Package | From | To |
| --- | --- | --- |
| [next](https://github.com/vercel/next.js) | `16.2.11` | `16.3.3` |
| [@types/react](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/react) | `19.2.17` | `19.2.18` |
| [@types/react-dom](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/react-dom) | `19.2.3` | `19.2.5` |
| [cnfast](https://github.com/aidenybai/cnfast/tree/HEAD/packages/cnfast) | `0.0.8` | `0.1.0` |
| [fumadocs-core](https://github.com/fuma-nama/fumadocs) | `16.10.7` | `16.15.4` |
| [fumadocs-mdx](https://github.com/fuma-nama/fumadocs) | `15.0.13` | `15.4.0` |

Bumps the npm-minor-patch group with 4 updates in the /apps/docs directory: [next](https://github.com/vercel/next.js), [cnfast](https://github.com/aidenybai/cnfast/tree/HEAD/packages/cnfast), [fumadocs-core](https://github.com/fuma-nama/fumadocs) and [fumadocs-mdx](https://github.com/fuma-nama/fumadocs).


Updates `next` from 16.2.11 to 16.3.3
- [Release notes](https://github.com/vercel/next.js/releases)
- [Commits](vercel/next.js@v16.2.11...v16.3.3)

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

Updates `@types/react-dom` from 19.2.3 to 19.2.5
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/react-dom)

Updates `cnfast` from 0.0.8 to 0.1.0
- [Release notes](https://github.com/aidenybai/cnfast/releases)
- [Changelog](https://github.com/aidenybai/cnfast/blob/main/packages/cnfast/CHANGELOG.md)
- [Commits](https://github.com/aidenybai/cnfast/commits/HEAD/packages/cnfast)

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

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

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

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

Updates `next` from 16.2.11 to 16.3.3
- [Release notes](https://github.com/vercel/next.js/releases)
- [Commits](vercel/next.js@v16.2.11...v16.3.3)

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

Updates `@types/react-dom` from 19.2.3 to 19.2.5
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/react-dom)

Updates `next` from 16.2.11 to 16.3.3
- [Release notes](https://github.com/vercel/next.js/releases)
- [Commits](vercel/next.js@v16.2.11...v16.3.3)

Updates `cnfast` from 0.0.8 to 0.1.0
- [Release notes](https://github.com/aidenybai/cnfast/releases)
- [Changelog](https://github.com/aidenybai/cnfast/blob/main/packages/cnfast/CHANGELOG.md)
- [Commits](https://github.com/aidenybai/cnfast/commits/HEAD/packages/cnfast)

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

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

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

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

Updates `next` from 16.2.11 to 16.3.3
- [Release notes](https://github.com/vercel/next.js/releases)
- [Commits](vercel/next.js@v16.2.11...v16.3.3)

---
updated-dependencies:
- dependency-name: "@types/react"
  dependency-version: 19.2.18
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: npm-minor-patch
- dependency-name: "@types/react"
  dependency-version: 19.2.18
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: npm-minor-patch
- dependency-name: "@types/react-dom"
  dependency-version: 19.2.4
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: npm-minor-patch
- dependency-name: "@types/react-dom"
  dependency-version: 19.2.4
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: npm-minor-patch
- dependency-name: cnfast
  dependency-version: 0.1.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: npm-minor-patch
- dependency-name: cnfast
  dependency-version: 0.1.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: npm-minor-patch
- dependency-name: fumadocs-core
  dependency-version: 16.14.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: npm-minor-patch
- dependency-name: fumadocs-core
  dependency-version: 16.14.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: npm-minor-patch
- dependency-name: fumadocs-core
  dependency-version: 16.14.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: npm-minor-patch
- dependency-name: fumadocs-core
  dependency-version: 16.14.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: npm-minor-patch
- dependency-name: fumadocs-mdx
  dependency-version: 15.2.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: npm-minor-patch
- dependency-name: fumadocs-mdx
  dependency-version: 15.2.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: npm-minor-patch
- dependency-name: fumadocs-mdx
  dependency-version: 15.2.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: npm-minor-patch
- dependency-name: fumadocs-mdx
  dependency-version: 15.2.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: npm-minor-patch
- dependency-name: next
  dependency-version: 16.2.12
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: npm-minor-patch
- dependency-name: next
  dependency-version: 16.2.12
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: npm-minor-patch
- dependency-name: next
  dependency-version: 16.2.12
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: npm-minor-patch
- dependency-name: next
  dependency-version: 16.2.12
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: npm-minor-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/npm-minor-patch-a18a6ef387 branch from 30c1241 to 6cb8bfa Compare September 5, 2026 00:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants