Skip to content

chore(deps): bump the docs-tooling group across 1 directory with 7 updates - #556

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/docs-tooling-320d432a64
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/docs-tooling-320d432a64

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 28, 2026 •

Copy link
Copy Markdown
Contributor

Bumps the docs-tooling group with 7 updates in the / directory:

Package From To
fumadocs-core 16.15.4 16.15.17
fumadocs-mdx 15.4.0 15.4.5
fumadocs-twoslash 3.3.0 4.0.1
fumadocs-ui 16.15.4 16.15.17
lucide-react 1.35.0 1.48.0
mermaid 11.17.2 12.0.0
next 16.3.6 16.3.7

Updates fumadocs-core from 16.15.4 to 16.15.17

Release notes

Sourced from fumadocs-core's releases.

fumadocs@16.15.17

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

Apply the Vite base path to the "View as Markdown" link

<ViewOptionsPopover /> linked to markdownUrl without the Vite base, so sites served under a base path got a 404. It now prefixes the URL like <MarkdownCopyButton /> does.

Fix #3620

fumadocs@16.15.16

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

Don't copy failed Markdown responses

<MarkdownCopyButton /> copied the body of error responses, like a 404 page, and kept it cached until a full reload. Failed responses are rejected, and only successful ones are cached.

Fix #3612

Get pages by decoded slugs

getPage() accepts both URI encoded and decoded slugs. React Router and TanStack Router pass decoded params, so pages with spaces or non-ASCII characters in their slugs were not found.

Fix #3613

fumadocs@16.15.15

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

Fix infinite recursion in the MDX stringifier with mdast-util-to-markdown@2.1.3

The stringifier wraps every toMarkdown handler but dropped their attention and peek properties, which mdast-util-to-markdown@2.1.3 relies on to serialize bold and italic text. Pages containing them overflowed the stack during build.

fumadocs@16.15.14

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

Announce copy confirmation to screen readers

Copy buttons are polite live regions whose label switches to "Copied" after a successful copy, so screen readers announce it. The code block's copy button no longer reports success when the clipboard write fails.

Expose the search dialog as a combobox

The search input is now a combobox that controls a listbox of option results and reports the highlighted result through aria-activedescendant, so screen readers announce results as you move through them. Hidden result buttons are removed from the tab order, and the empty state is announced as a status message.

... (truncated)

Commits

Updates fumadocs-mdx from 15.4.0 to 15.4.5

Release notes

Sourced from fumadocs-mdx's releases.

fumadocs-mdx@15.4.5

Stop recrawling node_modules on every Vite config resolution

The config hook of fumadocs-mdx/vite walked the dependency tree below Fumadocs packages once per chain reaching a package, so a docs app with a few Fumadocs packages read ~10k package.json files (~0.9s) each time Vite resolved its config, which it does once per build environment.

The crawl now visits each package once, breadth-first, and still records the shortest chain to every CommonJS dependency (fumadocs-ui > @base-ui/react > use-sync-external-store/shim and friends). The result is memoized for the process until the package manager's install state changes, so a build with several environments crawls once.

fumadocs-mdx@15.4.4

Sort glob results for deterministic codegen

fumadocs-mdx's Node codegen now sorts glob-matched files before generating collections, so the output (and anything derived from getPages()) is stable across builds of unchanged content. The Vite codegen path was checked separately: Vite's own import.meta.glob already sorts matched files internally, so it did not need the same fix.

fumadocs-mdx@15.4.3

Fix experimentalBuildCache bloating frontmatter-only imports

With a warm build cache, ?only=frontmatter imports were served the fully compiled page from cache instead of the frontmatter module, so every page was bundled two more times. The cache now only applies to full compilations.

fumadocs-mdx@15.4.2

Fix the _mdast export with removePosition

// fumadocs-mdx collection config
postprocess: {
  includeMDAST: { removePosition: true },
},

This exported _mdast with no value, and getMDAST() then reported that includeMDAST was disabled. removePosition strips positions in place and returns nothing, so JSON.stringify received undefined.

The tree is now cloned, stripped, and serialized from the clone.

Fix SOURCEMAP_BROKEN warnings on Vite

With build.sourcemap enabled, Vite warned once per content and meta file because the loaders returned no source map. They now return an empty map when nothing is generated.

Source maps for MDX stay opt-in, pass SourceMapGenerator from source-map to MDX options:

import { SourceMapGenerator } from 'source-map';
export default defineConfig({
mdxOptions: {
SourceMapGenerator,
},
});

fumadocs-mdx@15.4.1

Mark packages side-effect free

... (truncated)

Commits
  • cb6f3d6 Version Packages (#3600)
  • 6676327 perf(mdx): reduce duplicated file reads
  • f1186d9 fix(openapi): normalize fetch methods
  • a8438dc Version Packages (#3595)
  • 539bada feat(ui): support block toc variant
  • 23bef0b docs: correct stale info
  • e988e54 fix(ui): announce copy confirmation to screen readers
  • 583e2ca fix(ui): keep search dialog active state inside the list
  • 11bc9dc fix(ui): expose the search dialog as a combobox
  • d7fa38c fix(ui): remove hidden sidebar controls from the tab order
  • Additional commits viewable in compare view

Updates fumadocs-twoslash from 3.3.0 to 4.0.1

Release notes

Sourced from fumadocs-twoslash's releases.

fumadocs-twoslash@4.0.1

Mark packages side-effect free

All packages now declare sideEffects in package.json, so bundlers can tree-shake unused modules. Packages shipping stylesheets list them as side effects to keep CSS imports.

fumadocs-twoslash@4.0.0

Run Twoslash on TypeScript 7

fumadocs-twoslash now runs on the native TypeScript 7 compiler (typescript/unstable/sync) instead of bundling its own TypeScript 6, so the types in popups come from the same compiler as your project.

Code blocks of documents compiled concurrently are analyzed together in one snapshot of the TypeScript project (requires fumadocs-core 16.15.7 for the _fd_prepare hook of rehype-code), which removes most of the per-block cost of loading the project. Cold builds of the Fumadocs docs take 40% less time in total, with the TypeScript part 3.5x faster.

The Shiki transformer and renderer are now implemented in fumadocs-twoslash, @shikijs/twoslash and twoslash are no longer dependencies (nor twoslash a peer of TypeScript 6). The rendered HTML and the transformer options are unchanged, except that rendererRich only takes the options that apply to the popups of Fumadocs (jsdoc, processHoverInfo, processHoverDocs, completionIcons, customTagIcons); the hast extensions, errorRendering, queryRendering, classExtra and the custom renderer option are removed.

The twoslashOptions are simplified to what the native API supports:

  • compilerOptions takes tsconfig.json values (e.g. moduleResolution: 'bundler') instead of enum values from the typescript package.
  • cwd replaces vfsRoot.
  • tsModule, tsLibDirectory, fsMap, cache, customTransformers and the per-call positionQueries, positionCompletions, positionHighlights are removed.
  • @showEmit is not supported, TypeScript 7 has no emit API yet.
transformerTwoslash({
  twoslashOptions: {
    compilerOptions: {
      types: ['node'],
    },
  },
});

fumadocs-twoslash@3.3.1

Replace cnfast with cn

Internal refactor only.

Bundle TypeScript for Twoslash

fumadocs-twoslash now depends on its own TypeScript 6 and passes it to Twoslash, so the transformer keeps working in projects on TypeScript 7 (whose package no longer provides the compiler API Twoslash requires). Previously, every Twoslash code block that was not already in the types cache failed with Cannot read properties of undefined (reading 'readFile').

Commits

Updates fumadocs-ui from 16.15.4 to 16.15.17

Release notes

Sourced from fumadocs-ui's releases.

fumadocs@16.15.17

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

Apply the Vite base path to the "View as Markdown" link

<ViewOptionsPopover /> linked to markdownUrl without the Vite base, so sites served under a base path got a 404. It now prefixes the URL like <MarkdownCopyButton /> does.

Fix #3620

fumadocs@16.15.16

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

Don't copy failed Markdown responses

<MarkdownCopyButton /> copied the body of error responses, like a 404 page, and kept it cached until a full reload. Failed responses are rejected, and only successful ones are cached.

Fix #3612

Get pages by decoded slugs

getPage() accepts both URI encoded and decoded slugs. React Router and TanStack Router pass decoded params, so pages with spaces or non-ASCII characters in their slugs were not found.

Fix #3613

fumadocs@16.15.15

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

Fix infinite recursion in the MDX stringifier with mdast-util-to-markdown@2.1.3

The stringifier wraps every toMarkdown handler but dropped their attention and peek properties, which mdast-util-to-markdown@2.1.3 relies on to serialize bold and italic text. Pages containing them overflowed the stack during build.

fumadocs@16.15.14

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

Announce copy confirmation to screen readers

Copy buttons are polite live regions whose label switches to "Copied" after a successful copy, so screen readers announce it. The code block's copy button no longer reports success when the clipboard write fails.

Expose the search dialog as a combobox

The search input is now a combobox that controls a listbox of option results and reports the highlighted result through aria-activedescendant, so screen readers announce results as you move through them. Hidden result buttons are removed from the tab order, and the empty state is announced as a status message.

... (truncated)

Commits

Updates lucide-react from 1.35.0 to 1.48.0

Release notes

Sourced from lucide-react's releases.

Version 1.48.0

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@1.47.0...1.48.0

Version 1.47.0

What's Changed

New Contributors

... (truncated)

Commits

Updates mermaid from 11.17.2 to 12.0.0

Release notes

Sourced from mermaid's releases.

mermaid@12.0.0

Mermaid 12.0.0 ships ELK as the bundled default layout engine, a new redux-color / neo default appearance, and two new diagram types: UML use case diagrams.

This is a breaking release (ES2024, Safari 17.4+, Node 22.12+). Existing flowcharts, state and class diagrams will re-lay out and recolour; add layout: dagre, theme: default and look: classic to your config to keep the old look. Full changelog below.

Major Changes

  • #8213 33442fd Thanks @​aloisklink! - chore!: require ES2024, Safari 17.4+, Node.JS v22.12+

    Mermaid is now built to target Safari 17.4+ and ES2024. If you need to support older browsers, you may need to polyfill or transpile mermaid.

    Safari 17.4+ has been chosen as the floor, as unlike Firefox/Chrome, older iOS devices don't get major Safari updates.

    Node.JS v22.12+ is also declared as requirement in our package.json files, but as mermaid requires a browser, this is mainly so we can use dependencies that also declare a Node.JS v22.12+ requirement, without causing issues for users when running npm install.

  • #8155 810893c Thanks @​ashishjain0512! - feat!: ELK is now bundled with mermaid and is the default layout algorithm.

    ELK previously shipped as a separate @mermaid-js/layout-elk package that sites had to install and register. It is now part of mermaid itself and registered automatically, so layout: elk — and the elk.stress, elk.force, elk.mrtree, elk.sporeOverlap, elk.box and elk.rectpacking variants — work with no setup.

    This changes how existing diagrams look. Flowchart, state, class, entity-relationship, requirement, use-case diagrams that do not specify a layout are now laid out by ELK instead of dagre. To keep the previous layout, set dagre explicitly:

    ---
    config:
      layout: dagre
    ---

    or globally, mermaid.initialize({ layout: 'dagre' }).

    Mindmap is unchanged: it keeps laying out with cose-bilkent unless a layout is explicitly requested (in the tiny build, which ships neither ELK nor cose-bilkent, it falls back to dagre).

    Other notes:

    • ELK is loaded as a separate chunk in the ESM builds, so it is only fetched when a diagram actually uses it. The single-file IIFE build (mermaid.min.js) inlines it and grows by roughly 500 kB gzipped.
    • The tiny build deliberately omits ELK to stay small, and falls back to dagre for diagrams that ask for an ELK layout. Its size is unchanged.
    • @mermaid-js/layout-elk is no longer needed on normal builds — existing mermaid.registerLayoutLoaders(elkLayouts) calls keep working and can be removed. It is still published, and remains the way to add ELK to the tiny build.
    • dist/mermaid.esm.min.mjs now contains syntax that es-module-lexer (used by Vite) rejects with content contains invalid JS syntax. Bundler users are unaffected as long as they import the mermaid package specifier, which resolves to the core build; only builds that point Vite directly at that dist file need to switch to the package specifier or the core build.
    • State diagrams now resolve their layout through the same registration check as every other diagram, so an unavailable layout falls back instead of failing to render.

    An unrecognised theme name now resolves to the default theme in name as well as in variables; previously the invalid name stayed in place while the default's variables were loaded, and every palette-aware stylesheet gates on the name. theme: 'null', the documented way to disable the pre-defined themes, is unaffected. Note that neo paints node strokes with a gradient when the theme sets useGradient, which base does; setting a custom nodeBorder on base turns the gradient off.

  • #8211 a19bd08 Thanks @​ashishjain0512! - Removed: the defaultRenderer option of the flowchart, class and state config sections.

    Use the top-level layout option instead:

... (truncated)

Commits
  • 98a0945 Merge pull request #8237 from mermaid-js/changeset-release/master
  • 96be564 Version Packages
  • dd65cfd Merge pull request #8239 from mermaid-js/bug/appearance-docs-release-version-...
  • e1cc7c2 fix(tests): accept a released version in the appearance docs marker
  • 8382837 Merge pull request #8211 from mermaid-js/release/12.0.0
  • 8a90389 ci: trigger a preview publish
  • 01b8590 ci: attempt every preview package before failing the publish step
  • 1997a23 ci: record why the preview publish of layout-elk and tiny is refused
  • 0304007 ci: drop --access public from the preview publish of layout-elk and tiny
  • 223be92 docs: capitalize Markdown in README tagline
  • Additional commits viewable in compare view

Updates next from 16.3.6 to 16.3.7

Release notes

Sourced from next's releases.

v16.3.7

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

Core Changes

  • turbo-tasks-backend: fix strongly consistent read hanging on a canceled task (#98931)

Credits

Huge thanks to @​lukesandberg for helping!

Commits
  • 4c20699 v16.3.7
  • 2521aec [backport] turbo-tasks-backend: fix strongly consistent read hanging on a can...
  • See full diff in compare view

@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label Sep 28, 2026
@dependabot
dependabot Bot requested a review from solidsnakedev as a code owner September 28, 2026 09:18
@solidsnakedev

solidsnakedev commented Sep 28, 2026 •

Copy link
Copy Markdown
Collaborator

Skipped: CI failing: Build.

@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/docs-tooling-320d432a64 branch 2 times, most recently from 0708dff to d89e8eb Compare September 28, 2026 20:23
…dates

Bumps the docs-tooling group with 7 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [fumadocs-core](https://github.com/fuma-nama/fumadocs) | `16.15.4` | `16.15.17` |
| [fumadocs-mdx](https://github.com/fuma-nama/fumadocs) | `15.4.0` | `15.4.5` |
| [fumadocs-twoslash](https://github.com/fuma-nama/fumadocs) | `3.3.0` | `4.0.1` |
| [fumadocs-ui](https://github.com/fuma-nama/fumadocs) | `16.15.4` | `16.15.17` |
| [lucide-react](https://github.com/lucide-icons/lucide/tree/HEAD/packages/lucide-react) | `1.35.0` | `1.48.0` |
| [mermaid](https://github.com/mermaid-js/mermaid) | `11.17.2` | `12.0.0` |
| [next](https://github.com/vercel/next.js) | `16.3.6` | `16.3.7` |



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

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

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

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

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

Updates `mermaid` from 11.17.2 to 12.0.0
- [Release notes](https://github.com/mermaid-js/mermaid/releases)
- [Commits](https://github.com/mermaid-js/mermaid/compare/mermaid@11.17.2...mermaid@12.0.0)

Updates `next` from 16.3.6 to 16.3.7
- [Release notes](https://github.com/vercel/next.js/releases)
- [Commits](vercel/next.js@v16.3.6...v16.3.7)

---
updated-dependencies:
- dependency-name: fumadocs-core
  dependency-version: 16.15.14
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: docs-tooling
- dependency-name: fumadocs-mdx
  dependency-version: 15.4.5
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: docs-tooling
- dependency-name: fumadocs-twoslash
  dependency-version: 4.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: docs-tooling
- dependency-name: fumadocs-ui
  dependency-version: 16.15.14
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: docs-tooling
- dependency-name: lucide-react
  dependency-version: 1.48.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: docs-tooling
- dependency-name: mermaid
  dependency-version: 12.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: docs-tooling
- dependency-name: next
  dependency-version: 16.3.6
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: docs-tooling
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/docs-tooling-320d432a64 branch from d89e8eb to 2ce94b1 Compare September 30, 2026 18:55

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant