Update non-major dependencies

[renovate]

Summary

Updates non-major dependencies in the workspace lockfile (pnpm-lock.yaml). No application source code was modified; the changes are limited to dependency resolution and the version specifiers recorded for the documentation packages.

Dependency Updates

Package	From	To
posthog-js	1.438.3	1.438.4
fumadocs-core	16.16.2	16.17.0
fumadocs-mdx	15.4.6	15.4.7
@fumadocs/base-ui (aliased as fumadocs-ui)	16.16.2	16.17.0
@fumadocs/tailwind	0.1.2	0.1.3
yuku-analyzer	0.10.2	0.17.0
yuku-ast	0.10.2	0.17.0
@yuku-toolchain/types	0.10.2	0.17.0

Notable Transitive Changes

• yuku-core introduced at 0.17.0. The platform-specific optional bindings previously published as @yuku-analyzer/binding-* (0.10.2) are now published as @yuku-core/binding-* (0.17.0) for all supported OS/architecture targets (Android, Darwin, FreeBSD, Linux, Windows). The prior packages carried a deprecation notice stating that yuku-analyzer runs on yuku-core since 0.14. yuku-analyzer@0.17.0 now depends on yuku-core, yuku-ast, and @yuku-toolchain/types, and declares a Node engine requirement of >=14.18.0 (also added for yuku-ast and yuku-core).
• fumadocs-core dependency graph adjusted. Added hast-util-from-dom, micromark, and micromark-extension-gfm-table (resolved to 2.1.2); removed mdast-util-to-markdown and unist-util-visit from its dependency list.
• @fumadocs/base-ui dependency graph adjusted. Added hast-util-to-jsx-runtime; removed rehype-raw and unist-util-visit.
• Removed packages no longer required by the tree: rehype-raw, hast-util-raw, hast-util-from-parse5, hast-util-to-parse5, parse5, vfile-location, and entities@6.0.1.
• fumadocs-mdx peer requirement tightened: its fumadocs-core peer range is now ^16.17.0 (previously ^16.15.3), matching the updated fumadocs-core version.
• @fumadocs/base-ui now resolves supports-color as a transitive peer dependency.

Impact

• Lockfile-only change; no functional code paths were touched in this diff.
• The fumadocs suite (core, mdx, base-ui, tailwind) moves forward together in a compatible set, keeping documentation tooling on consistent versions.
• The yuku-* toolchain advances from 0.10.2 to 0.17.0, migrating to the consolidated yuku-core native bindings; the new packages require Node >=14.18.0.

Verification

• Automated code review completed with no issues reported.

[kody-ai]

Kody Review Complete

Great news! 🎉
No issues were found that match your current review configurations.

Keep up the excellent work! 🚀

⚠️ 1 Kody Rule(s) were not evaluated

These rules declare that they need repository context beyond this diff, and the review could not retrieve it, so they were not judged on this pull request:

• Prefer Sentry for new observability; do not add new Datadog RUM/APM surfaces

Kody Guide: Usage and Configuration

Interacting with Kody

• Request a Review: Ask Kody to review your PR manually by adding a comment with the @kody start-review command at the root of your PR.

• Validate Business Logic: Ask Kody to validate your code against business rules by adding a comment with the @kody -v business-logic command.

• Provide Feedback: Help Kody learn and improve by reacting to its comments with a 👍 for helpful suggestions or a 👎 if improvements are needed.

Current Kody Configuration

Review Options

The following review options are enabled or disabled:

Options	Enabled
Bug	✅
Performance	✅
Security	✅
Business Logic	✅

Access your configuration settings here.

​