📦 chore: update deps

[lorenzopantano]

No description provided.

[qodo-code-review]

Review Summary by Qodo

Update dependencies to latest available versions

✨ Enhancement

Walkthroughs

Description

• Update multiple dependencies to latest versions
• Upgrade fumadocs packages to 16.7.14 and 14.2.13
• Update framer-motion, react, and image-response packages
• Refresh pnpm lock file with new dependency versions

Diagram

flowchart LR
  A["Package Dependencies"] -- "upgrade versions" --> B["fumadocs packages"]
  A -- "upgrade versions" --> C["framer-motion"]
  A -- "upgrade versions" --> D["react & image-response"]
  B --> E["Lock File Updated"]
  C --> E
  D --> E

Loading

File Changes

1. apps/docs/package.json Dependencies +7/-7

Bump multiple package versions in docs app

• Updated @takumi-rs/image-response from 0.73.1 to 1.0.9
• Updated framer-motion from 12.34.3 to 12.38.0
• Updated fumadocs-core from 16.6.5 to 16.7.14
• Updated fumadocs-mdx from 14.2.8 to 14.2.13
• Updated fumadocs-typescript from 5.1.4 to 5.2.4
• Updated fumadocs-ui from 16.6.5 to 16.7.14
• Updated react from 19.2.4 to 19.2.5

apps/docs/package.json

---

2. pnpm-lock.yaml Dependencies +640/-916

Regenerate lock file with new versions

• Regenerated lock file to reflect updated dependency versions
• Updated transitive dependencies and checksums

pnpm-lock.yaml

---

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (1)   📘 Rule violations (0)   📎 Requirement gaps (0)

🐞\ ☼ Reliability (1)

1. Node 20 required now 🐞 ☼

Description

The updated dependency graph includes shiki@4.x / @shikijs/* which declare `engines: { node: ">=20"
}`. Without declaring/enforcing Node >=20 at the repo/app level, installs or docs tooling will break
for any environment still using Node 18/19.

Code

pnpm-lock.yaml[R3005-3007]

+  shiki@4.0.2:
+    resolution: {integrity: sha512-eAVKTMedR5ckPo4xne/PjYQYrU3qx78gtJZ+sHlXEg5IHhhoQhMfZVzetTYuaJS0L2Ef3AcCRzCHV8T0WI6nIQ==}
+    engines: {node: '>=20'}

Evidence

The lockfile now contains Shiki v4 packages that require Node >=20, while the repository root does
not declare an engines constraint; CI happens to use Node 20 but local/prod environments may not.

pnpm-lock.yaml[1472-1478]
pnpm-lock.yaml[3005-3007]
.github/workflows/ci.yml[23-27]
package.json[1-34]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The updated deps introduce packages (e.g., `shiki@4.x`) that require Node.js >=20, but the repo does not formally declare this requirement. This can cause installation/tooling failures for contributors or deployments running Node <20.
### Issue Context
CI uses Node 20, but local/dev/prod environments may differ unless the minimum Node version is declared and enforced.
### Fix Focus Areas
- pnpm-lock.yaml[1472-1478]
- pnpm-lock.yaml[3005-3007]
- .github/workflows/ci.yml[23-27]
- package.json[1-34]
### Suggested fix (pick one)
**Option A (recommended if Node >=20 is intended):**
1. Add an `engines` field (e.g., `{ "node": ">=20" }`) to the root `package.json` (and/or `apps/docs/package.json`).
2. Optionally add a `.nvmrc` or `.node-version` file set to `20` to guide local development.
3. Document the requirement in README(s).
**Option B (if Node <20 must remain supported):**
Pin/adjust the upgraded docs deps to versions that do not pull in `shiki@4` / `@shikijs/*@4` (Node>=20) and regenerate the lockfile accordingly.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

2. React/ReactDOM patch mismatch ☑ 🐞 ☼

Description

apps/docs declares react ^19.2.5 while react-dom remains ^19.2.4, and the lockfile resolves them to
different patch versions. This leaves the docs app running React and ReactDOM out of sync, which is
a common source of avoidable runtime/library incompatibilities.

Code

apps/docs/package.json[R34-35]

+		"react": "^19.2.5",
"react-dom": "^19.2.4",

Evidence

The docs app explicitly declares different patch versions, and the lockfile confirms the install
will use react@19.2.5 alongside react-dom@19.2.4.

apps/docs/package.json[33-36]
pnpm-lock.yaml[68-73]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`apps/docs` installs `react@19.2.5` but `react-dom@19.2.4`. Keep React and ReactDOM on the same version.
### Issue Context
The current `pnpm-lock.yaml` resolves `react` and `react-dom` to different patch versions.
### Fix Focus Areas
- apps/docs/package.json[33-36]
- pnpm-lock.yaml[68-73]
### Suggested fix
1. Update `apps/docs/package.json` to bump `react-dom` to `^19.2.5` (or otherwise make it match the chosen React version).
2. Re-run `pnpm install` (or `pnpm --filter docs up react-dom`) to update `pnpm-lock.yaml` so `react-dom` resolves to the matching version.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

ⓘ The new review experience is currently in Beta. Learn more

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
lorenzopant-tmdb-docs	Ready	Preview, Comment	Apr 15, 2026 7:39pm

[qodo-code-review]

1. Node 20 required now 🐞 Bug ☼ Reliability

The updated dependency graph includes shiki@4.x / @shikijs/* which declare `engines: { node: ">=20"
}`. Without declaring/enforcing Node >=20 at the repo/app level, installs or docs tooling will break
for any environment still using Node 18/19.

Agent Prompt

### Issue description
The updated deps introduce packages (e.g., `shiki@4.x`) that require Node.js >=20, but the repo does not formally declare this requirement. This can cause installation/tooling failures for contributors or deployments running Node <20.

### Issue Context
CI uses Node 20, but local/dev/prod environments may differ unless the minimum Node version is declared and enforced.

### Fix Focus Areas
- pnpm-lock.yaml[1472-1478]
- pnpm-lock.yaml[3005-3007]
- .github/workflows/ci.yml[23-27]
- package.json[1-34]

### Suggested fix (pick one)
**Option A (recommended if Node >=20 is intended):**
1. Add an `engines` field (e.g., `{ "node": ">=20" }`) to the root `package.json` (and/or `apps/docs/package.json`).
2. Optionally add a `.nvmrc` or `.node-version` file set to `20` to guide local development.
3. Document the requirement in README(s).

**Option B (if Node <20 must remain supported):**
Pin/adjust the upgraded docs deps to versions that do not pull in `shiki@4` / `@shikijs/*@4` (Node>=20) and regenerate the lockfile accordingly.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools