Bump the all group across 1 directory with 11 updates

[dependabot]

Bumps the all group with 11 updates in the /web-docs directory:

Package	From	To
fumadocs-core	16.14.4	16.15.4
fumadocs-mdx	15.2.3	15.4.0
fumadocs-ui	16.14.2	16.15.4
input-otp	1.4.2	1.5.0
lucide-react	1.31.0	1.35.0
motion	12.43.0	13.1.1
next	16.3.0	16.3.3
@biomejs/biome	2.5.8	2.5.11
@types/node	26.2.0	26.4.0
@types/react-dom	19.2.4	19.2.5
vite	8.2.1	8.2.2

Updates fumadocs-core from 16.14.4 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.2.3 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-ui from 16.14.2 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 input-otp from 1.4.2 to 1.5.0

Release notes

Sourced from input-otp's releases.

v1.5.0

Promotes the safe 1.5.0-beta.2 code without functional changes. Everything in this release is backwards-compatible: no public type changes and no behavior changes beyond the bug fixes below. Two beta.1 experiments are deliberately excluded — the iOS native-selection workaround (the thin native selection artifact remains a known cosmetic limitation) and the onComplete type narrowing, which returns in 2.0.0 as a documented breaking change.

• fix(input): reserve the password manager badge gutter only where it fits
• fix(input): disable spellcheck by default
• fix(input): feature-detect ResizeObserver before observing
• fix(input): use a 16px fallback until --root-height resolves, preventing iOS focus zoom
• fix(input): clear pending synchronization timeouts on unmount
• feat(input): add a nonce prop for Content-Security-Policy support
• fix(input): guard the input reference used by the selectionchange listener
• fix(input): opt the container out of browser translation
• fix(input): report cosmetic CSS rule failures as warnings instead of errors
• docs: document the stable iOS selection behavior and its cosmetic limitation

Safe release candidate for 1.5.0. This release withdraws the experimental iOS native-selection workaround from 1.5.0-beta.1 after compatibility review. The edit menu, paste, typing, selection and focus behavior return to the proven 1.4.x implementation; the thin native selection artifact remains a known iOS limitation.

It also withdraws the onComplete type narrowing from 1.5.0-beta.1. Although type-level only, it can fail compilation of existing handlers typed with extra or non-string parameters (a common example is passing react-hook-form's handleSubmit(onSubmit) directly), which makes it a breaking change under semver. It will return in 2.0.0 with a documented migration path.

• revert(input): withdraw the experimental iOS native-selection workaround from 1.5.0-beta.1
• revert(types): withdraw the onComplete narrowing from 1.5.0-beta.1, deferring it to 2.0.0
• docs: align the mobile and edge-case documentation with the stable candidate
• test: verify focus, typing, editing, deletion, paste, Select All → Paste and the native edit menu on iOS 18.0 and 26.5 simulators

Deprecated experimental release. It introduced an iOS native-selection workaround that moved and scaled the underlying input, and narrowed the onComplete type in a way that can break compilation of existing apps. Both were withdrawn in 1.5.0-beta.2 and are not planned for 1.5.0 stable. Existing installs remain reproducible, but new beta users should use 1.5.0-beta.2 or later.

Prepared but not published. Its safe changes are included in 1.5.0-beta.2.

• fix(input): reserve the password manager badge gutter only where it fits
  • Once a badge was detected, the input grew 40px past the container to push the badge off the last slot — and the only guard was the distance to the viewport's right edge. Inside a constrained scroll container (a card, a modal) that overhang registered as scrollable overflow: a horizontal scrollbar appeared and shifted the whole layout. The space check now measures the nearest ancestor that constrains horizontal overflow (scroll containers, overflow: hidden/clip ancestors, the container itself, and the real viewport width) and skips the push when the gutter doesn't fit; the badge then stays over the last slot, exactly as with pushPasswordManagerStrategy="none". Nothing is ever clipped, so extensions keep rendering their badges.
• fix(input): disable spellcheck by default
  • Browsers would mark a filled code as a spelling error and underline it. spellCheck now defaults to false; passing your own spellCheck prop still overrides it.
• fix(input): feature-detect ResizeObserver before observing
  • Browsers without ResizeObserver (e.g. iOS Safari <13.4) crashed on mount. When the observer is unavailable, the root height is now simply measured once on mount.
• fix(input): fall back to 16px font-size until --root-height resolves
  • Before the variable is set, the invisible input inherited its font-size — and when that inherited size was under 16px, iOS Safari zoomed the whole page on focus or back-navigation.
• fix(input): clear pending sync timeouts on unmount
  • The autofill/selection sync timeouts could fire after unmount, causing state updates on an unmounted component — noisy act() warnings and flaky CI test runs.
• feat(input): add nonce prop
  • Applied to the <style> tag the library injects, so a style-src Content-Security-Policy that requires nonces no longer blocks it.
• fix(input): use the guarded input reference inside the selectionchange listener
  • Fixes a null is not an object (evaluating 'setSelectionRange') crash when the listener fired while the ref was already null.
• fix(input): opt the container out of browser translation
  • Chrome's translator rewrote the slots' text nodes (wrapping them in <font> elements), crashing React on the next re-render — easiest to hit with alphanumeric codes under an active page translation. The container now carries translate="no"; a one-time code is never meaningful to translate.
• fix(input): log CSS rule insertion failures as warnings, not errors
  • Some environments reject individual cosmetic selectors (:autofill in older Android WebViews, for instance). Nothing breaks when that happens, but the console.error was captured by Sentry and similar tools as if the application had failed. Same message, warning level.
• chore(types): narrow onComplete to (value: string) => unknown

... (truncated)

Changelog

Sourced from input-otp's changelog.

[1.5.0]

Promotes the safe 1.5.0-beta.2 code without functional changes. Everything in this release is backwards-compatible: no public type changes and no behavior changes beyond the bug fixes below. Two beta.1 experiments are deliberately excluded — the iOS native-selection workaround (the thin native selection artifact remains a known cosmetic limitation) and the onComplete type narrowing, which returns in 2.0.0 as a documented breaking change.

• fix(input): reserve the password manager badge gutter only where it fits
• fix(input): disable spellcheck by default
• fix(input): feature-detect ResizeObserver before observing
• fix(input): use a 16px fallback until --root-height resolves, preventing iOS focus zoom
• fix(input): clear pending synchronization timeouts on unmount
• feat(input): add a nonce prop for Content-Security-Policy support
• fix(input): guard the input reference used by the selectionchange listener
• fix(input): opt the container out of browser translation
• fix(input): report cosmetic CSS rule failures as warnings instead of errors
• docs: document the stable iOS selection behavior and its cosmetic limitation

[1.5.0-beta.2]

Safe release candidate for 1.5.0. This release withdraws the experimental iOS native-selection workaround from 1.5.0-beta.1 after compatibility review. The edit menu, paste, typing, selection and focus behavior return to the proven 1.4.x implementation; the thin native selection artifact remains a known iOS limitation.

It also withdraws the onComplete type narrowing from 1.5.0-beta.1. Although type-level only, it can fail compilation of existing handlers typed with extra or non-string parameters (a common example is passing react-hook-form's handleSubmit(onSubmit) directly), which makes it a breaking change under semver. It will return in 2.0.0 with a documented migration path.

• revert(input): withdraw the experimental iOS native-selection workaround from 1.5.0-beta.1
• revert(types): withdraw the onComplete narrowing from 1.5.0-beta.1, deferring it to 2.0.0
• docs: align the mobile and edge-case documentation with the stable candidate
• test: verify focus, typing, editing, deletion, paste, Select All → Paste and the native edit menu on iOS 18.0 and 26.5 simulators

[1.5.0-beta.1]

Deprecated experimental release. It introduced an iOS native-selection workaround that moved and scaled the underlying input, and narrowed the onComplete type in a way that can break compilation of existing apps. Both were withdrawn in 1.5.0-beta.2 and are not planned for 1.5.0 stable. Existing installs remain reproducible, but new beta users should use 1.5.0-beta.2 or later.

[1.5.0-beta.0]

Prepared but not published. Its safe changes are included in 1.5.0-beta.2.

• fix(input): reserve the password manager badge gutter only where it fits
  • Once a badge was detected, the input grew 40px past the container to push the badge off the last slot — and the only guard was the distance to the viewport's right edge. Inside a constrained scroll container (a card, a modal) that overhang registered as scrollable overflow: a horizontal scrollbar appeared and shifted the whole layout. The space check now measures the nearest ancestor that constrains horizontal overflow (scroll containers, overflow: hidden/clip ancestors, the container itself, and the real viewport width) and skips the push when the gutter doesn't fit; the badge then stays over the last slot, exactly as with pushPasswordManagerStrategy="none". Nothing is ever clipped, so extensions keep rendering their badges.
• fix(input): disable spellcheck by default
  • Browsers would mark a filled code as a spelling error and underline it. spellCheck now defaults to false; passing your own spellCheck prop still overrides it.
• fix(input): feature-detect ResizeObserver before observing
  • Browsers without ResizeObserver (e.g. iOS Safari <13.4) crashed on mount. When the observer is unavailable, the root height is now simply measured once on mount.
• fix(input): fall back to 16px font-size until --root-height resolves
  • Before the variable is set, the invisible input inherited its font-size — and when that inherited size was under 16px, iOS Safari zoomed the whole page on focus or back-navigation.
• fix(input): clear pending sync timeouts on unmount
  • The autofill/selection sync timeouts could fire after unmount, causing state updates on an unmounted component — noisy act() warnings and flaky CI test runs.
• feat(input): add nonce prop
  • Applied to the <style> tag the library injects, so a style-src Content-Security-Policy that requires nonces no longer blocks it.
• fix(input): use the guarded input reference inside the selectionchange listener
  • Fixes a null is not an object (evaluating 'setSelectionRange') crash when the listener fired while the ref was already null.
• fix(input): opt the container out of browser translation
  • Chrome's translator rewrote the slots' text nodes (wrapping them in <font> elements), crashing React on the next re-render — easiest to hit with alphanumeric codes under an active page translation. The container now carries translate="no"; a one-time code is never meaningful to translate.

... (truncated)

Commits

• See full diff in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for input-otp since your current version.

Updates lucide-react from 1.31.0 to 1.35.0

Release notes

Sourced from lucide-react's releases.

Version 1.35.0

What's Changed

• feat(icons): added ship-cargo icon by @​l0uisgrange in lucide-icons/lucide#4706
• feat(icons): added trailer icon by @​MadsMadsDk in lucide-icons/lucide#4405
• feat(icons): added galaxy icon by @​karsa-mistmere in lucide-icons/lucide#4715
• feat(lab): added bat icon to lab by @​RajnishKMehta in lucide-icons/lucide#3914
• fix(icons): correct "operater" typo to "operator" in equal-approximately by @​hovelopin in lucide-icons/lucide#4760
• fix(icons): changed ghost icon by @​jguddas in lucide-icons/lucide#3533
• feat(icons): added robot-arm icon by @​zoharma in lucide-icons/lucide#4447

New Contributors

• @​l0uisgrange made their first contribution in lucide-icons/lucide#4706
• @​MadsMadsDk made their first contribution in lucide-icons/lucide#4405
• @​hovelopin made their first contribution in lucide-icons/lucide#4760
• @​zoharma made their first contribution in lucide-icons/lucide#4447

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

Version 1.34.0

What's Changed

• fix: update icon design discussion template by @​jguddas in lucide-icons/lucide#4726
• chore(deps-dev): bump the preact-deps group with 2 updates by @​dependabot[bot] in lucide-icons/lucide#4738
• feat(icons): added mail-clock icon by @​ericfennis in lucide-icons/lucide#4722

Full Changelog: lucide-icons/lucide@1.33.0...1.34.0

Version 1.33.0

What's Changed

• feat(icons): add list-clock icon by @​lazerg in lucide-icons/lucide#4636
• feat(icons): add square-dimensions by @​samuelalake in lucide-icons/lucide#4547
• feat(icons): added usb-c-port icon by @​karsa-mistmere in lucide-icons/lucide#4556
• docs(site): correct Vanilla icon import casing by @​hugosmoreira in lucide-icons/lucide#4597
• feat(icons): added audio-lines-off icon by @​karsa-mistmere in lucide-icons/lucide#4589
• chore(icon-discussions): add icon design template by @​jguddas in lucide-icons/lucide#4691
• feat(icons): added mop icon by @​karsa-mistmere in lucide-icons/lucide#4682
• chore(scripts): Potential fix for code scanning alert no. 31: Inefficient regular expression by @​ericfennis in lucide-icons/lucide#4723
• chore(deps-dev): bump the svelte-deps group with 3 updates by @​dependabot[bot] in lucide-icons/lucide#4720
• feat(icon-discussions): close discussions with banned phrases by @​jguddas in lucide-icons/lucide#4692
• feat(icons): added midi-port icon by @​simoncoudeville in lucide-icons/lucide#3754

New Contributors

• @​hugosmoreira made their first contribution in lucide-icons/lucide#4597
• @​simoncoudeville made their first contribution in lucide-icons/lucide#3754

Full Changelog: lucide-icons/lucide@1.32.0...1.33.0

Version 1.32.0

What's Changed

• feat(icons): added car-battery icon by @​andreynaz4renko in lucide-icons/lucide#4088

... (truncated)

Commits

• 75b5516 chore(dev): upgrade ESLint to latest compatible stack (v10) (#4378)
• See full diff in compare view

Updates motion from 12.43.0 to 13.1.1

Changelog

Sourced from motion's changelog.

[13.1.1] 2026-08-18

Fixed

• Guard animation window access in non-browser runtimes.
• AnimatePresence: Improved compat with React 19 strict mode.

[13.1.0] 2026-08-10

Added

• Reorder: Multidimensional reorder.
• Reorder: Automatic axis detection.
• Reorder: RTL support.

[13.0.0] 2026-08-05

Changed

• Removed optional @emotion/is-prop-valid dependency in favour of explicit <MotionConfig isValidProp={isPropValid}>.

Fixed

• Hardware-accelerated SVG elements correctly apply final style on animation complete.
• AnimatePresence: Ensure nodes are marked as safe to remove when rendering propagate with no motion children.

Commits

• 1b037b0 v13.1.1
• d734481 Updating changelog
• 9b9190d Latest
• c07d12e Merge pull request #3752 from motiondivision/fix-3746-animatepresence-strictm...
• b497f1d Merge branch 'main' into fix-3746-animatepresence-strictmode-remount
• bbabb00 Merge pull request #3751 from motiondivision/worktree-fix-issue-3735
• 06540fa Merge branch 'main' into worktree-fix-issue-3735
• adaf7a4 v13.1.0
• e713759 Updating changelog
• bc81c03 Updating publish
• Additional commits viewable in compare view

Updates next from 16.3.0 to 16.3.3

Release notes

Sourced from next's releases.

v16.3.3

This release contains security fixes for the following advisories:

Critical:

• Unauthenticated Remote Code Execution on windows-hosted servers
• Unauthenticated Remote Code Execution in Image Optimization API when AVIF files are used

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

• [16.x] Turbopack: don't strip async-module runtime from shared runtime chunks by @​lukesandberg in vercel/next.js#96653
• [16.x] [turbopack] Add turbopack_ecmascript and turbopack_wasm's embeded FS to internal_assets_conditions by @​lukesandberg in vercel/next.js#96655
• [16.x] [turbopack] Collapse nested promises in the analyzer by @​sampoder in vercel/next.js#96675
• [16.x] fix(next/image): preserve image response after optimization by @​styfle in vercel/next.js#96733
• [16.3.x] Default deploy e2e tests to the repo next version by @​eps1lon in vercel/next.js#96900
• [backport] Bump @​swc/helpers by @​mischnic in vercel/next.js#96885
• [backport] [turbopack] Raise registration calls in hoisted modules to the top by @​lukesandberg in vercel/next.js#97308
• [backport] Fix missing styled-jsx styles in Pages Router SSR on adapter builds by @​lukesandberg in vercel/next.js#97302
• [backport] [turbopack] Fix HMR for dynamic imports evaluated from layouts by @​lukesandberg in vercel/next.js#97317
• [backport] Restore the live headers() view of the incoming request by @​unstubbable in vercel/next.js#97311
• [backport] Allow literal exports in 'use cache' files by @​unstubbable in vercel/next.js#97312
• [backport] Keep the dev validation worker alive across HMR updates by @​unstubbable in vercel/next.js#97315
• [backport] Discard only cache entries that predate a tag revalidation, and reuse completed entries by @​unstubbable in vercel/next.js#97314
• [backport] Encode the cache item name built by unstable_cache by @​unstubbable in vercel/next.js#97313
• [16.3] [ci] Use OIDC tokens to read private preview builds by @​eps1lon in vercel/next.js#97258
• [backport] [test] Compile the middleware redirect routes up front in dev by @​lukesandberg in vercel/next.js#97328
• [backport] Fix Nav Inspector request loop on repeat captures by @​acdlite in vercel/next.js#97326
• [backport] Fix: Optimistic routing bugs leading to repeated prefetch loops by @​acdlite in vercel/next.js#97325
• [backport] Retain fewer stale cache versions and use a TTL, plus the mtime fallback by @​lukesandberg in vercel/next.js#97304
• [backport] Revert i18n localization change for dynamic Pages API routes (#94905) by @​gaojude in vercel/next.js#97330

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 @biomejs/biome from 2.5.8 to 2.5.11

Release notes

Sourced from @​biomejs/biome's releases.

Biome CLI v2.5.11

2.5.11

Patch Changes

• #11499 9743d0c Thanks @​scs0209! - Fixed #11496: useValidAnchor now treats Astro JSX shorthand attributes like <a {href}> as a valid href.

• #11437 88f805e Thanks @​Princesseuh! - Fixed #9944: adjacent elements inside an Astro expression now parse as an implicit fragment instead of raising an error.

  {options.map(() =>
    <div />
    <div />
  )}

• #11437 88f805e Thanks @​Princesseuh! - Fixed Astro templates rejecting unclosed HTML void elements, such as {cond && <br>}.

• #11507 e2fc036 Thanks @​dyc3! - Fixed #11157: noUnusedVariables no longer reports Vue <script setup> bindings used by CSS v-bind() as unused.

• #11398 afc4615 Thanks @​dyc3! - Fixed #11389: Files passed through --stdin-file-path now use full HTML support for Astro, Svelte, and Vue when it is enabled.

• #11526 372cd68 Thanks @​dyc3! - Fixed noVueRefAsOperand to track Vue refs through declaration aliases and toRefs() properties, and to recognize useTemplateRef() results. The rule no longer reports false positives such as plain ref transfers, plain toRefs() property access, defineModel() modifiers, or the supported .effect member as operands.

  The refactor enabling these fixes also improves the performance of the rule.

• #11458 a7cd286 Thanks @​dyc3! - Fixed #11436: GritQL snippets such as export { $specifiers } from $source now match named re-exports with aliases, inline type modifiers, and multiple specifiers.

• #11515 382b15d Thanks @​dyc3! - Fixed #11390, where noFloatingPromises performed expensive full type inference for calls to non-Promise methods declared on third-party TypeScript classes. The rule now classifies those calls using targeted type information.

• #11516 6f40e82 Thanks @​levrik! - Fixed noVueRefAsOperand so it no longer reports a callback parameter (e.g. from .find(), .map()) as an unwrapped ref value just because it's nested inside a ref(), computed(), or similar call.

  const result = computed(() => list.find((item) => item.label === "a"));

  Previously, item here was incorrectly treated as a ref value because the rule attributed it to the outer computed() call.

• #11495 496268d Thanks @​Netail! - Fixed useGraphqlNamingConvention so it no longer reports GraphQL enum value definitions with comments & descriptions and now displays a more accurate diagnostic range.

• #11407 6ef52b0 Thanks @​1678092075! - Fixed #11214: noUnusedVariables no longer reports type parameters declared by non-default function overload signatures that have an implementation.

• #11322 5c353e6 Thanks @​jp-knj! - Added a new nursery rule noAstroSetHtmlDirective, which disallows Astro's set:html directive because untrusted content can introduce cross-site scripting vulnerabilities.

  For example, the following snippet triggers the rule:

  <div set:html={content} />

... (truncated)

Changelog

Sourced from @​biomejs/biome's changelog.

2.5.11

Patch Changes

• #11499 9743d0c Thanks @​scs0209! - Fixed #11496: useValidAnchor now treats Astro JSX shorthand attributes like <a {href}> as a valid href.

• #11437 88f805e Thanks @​Princesseuh! - Fixed #9944: adjacent elements inside an Astro expression now parse as an implicit fragment instead of raising an error.

  {options.map(() =>
    <div />
    <div />
  )}

• #11437 88f805e Thanks @​Princesseuh! - Fixed Astro templates rejecting unclosed HTML void elements, such as {cond && <br>}.

• #11507 e2fc036 Thanks @​dyc3! - Fixed #11157: noUnusedVariables no longer reports Vue <script setup> bindings used by CSS v-bind() as unused.

• #11398 afc4615 Thanks @​dyc3! - Fixed #11389: Files passed through --stdin-file-path now use full HTML support for Astro, Svelte, and Vue when it is enabled.

• #11526 372cd68 Thanks @​dyc3! - Fixed noVueRefAsOperand to track Vue refs through declaration aliases and toRefs() properties, and to recognize useTemplateRef() results. The rule no longer reports false positives such as plain ref transfers, plain toRefs() property access, defineModel() modifiers, or the supported .effect member as operands.

  The refactor enabling these fixes also improves the performance of the rule.

• #11458 a7cd286 Thanks @​dyc3! - Fixed #11436: GritQL snippets such as export { $specifiers } from $source now match named re-exports with aliases, inline type modifiers, and multiple specifiers.

• #11515 382b15d Thanks @​dyc3! - Fixed #11390, where noFloatingPromises performed expensive full type inference for calls to non-Promise methods declared on third-party TypeScript classes. The rule now classifies those calls using targeted type information.

• #11516 6f40e82 Thanks @​levrik! - Fixed noVueRefAsOperand so it no longer reports a callback parameter (e.g. from .find(), .ma...

  Description has been truncated

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 32b9f812bc

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Upgrade the aliased Fumadocs UI with core

This raises fumadocs-core to 16.15.4 while fumadocs-ui still aliases @fumadocs/base-ui@16.14.2; the committed lock metadata for that UI package declares an exact fumadocs-core: 16.14.2 peer dependency. Every docs install therefore gets an unsupported UI/core pairing, even though this dependency update claims to upgrade both to 16.15.4. Update the alias and corresponding lock entry to the matching release.

Useful? React with 👍 / 👎.