Chore/20251014

[SvenVw]

Summary by CodeRabbit

• Chores
  • Upgraded PNPM project-wide and updated CI workflows to use the newer PNPM setup for docs, tests, and releases.
  • Refreshed dependencies across apps and packages (React, Router, Sentry, Tailwind, Docusaurus, mapping, analytics, and build tools) with minor/patch bumps.
  • Updated workspace tooling (TypeScript, Rollup, Vite, and related) for compatibility.
  • No functional or public API changes; maintenance and developer tooling stability improved.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 78e376a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Walkthrough

Bumps pnpm from 10.17.0 (and some earlier pins) to 10.18.3 across CI workflows and packageManager fields. Also updates numerous dependency and devDependency versions in fdm-app, fdm-docs, fdm-core, root package.json, and pnpm-workspace.yaml. No source code or exported API changes.

Changes

Cohort / File(s)	Summary
CI workflows (pnpm setup) .github/workflows/deploy-docs-test.yml, .github/workflows/deploy-docs.yml, \.github/workflows/release.yml, \.github/workflows/tests.yml	Update pnpm/action-setup steps to install pnpm 10.18.3 (from 10.17.0); no other workflow logic changed.
App dependencies update fdm-app/package.json	Bump many deps/devDeps across React ecosystem, routing, Sentry, Tailwind, map/geo libs, PostHog, framer-motion, lucide-react, vite tooling; packageManager → pnpm@10.18.3.
Docs dependencies update fdm-docs/package.json	Upgrade Docusaurus stack and related devDeps, React → 19.2.0, typedoc/related plugins; packageManager → pnpm@10.18.3.
Core deps update fdm-core/package.json	Bump @electric-sql/pglite, nanoid, @types/node; packageManager → pnpm@10.18.3.
PackageManager bumps only fdm-calculator/package.json, fdm-data/package.json	Update packageManager to pnpm@10.18.3; no other changes.
Root tooling update package.json	Update dev tooling: @biomejs/biome, turbo; packageManager → pnpm@10.18.3.
Workspace catalog bumps pnpm-workspace.yaml	Update workspace pinned versions (dotenvx, rollup & plugins, better-auth, drizzle-kit/orm, typedoc & plugins, typescript, vite, etc.).

Sequence Diagram(s)

(omitted — changes are dependency and CI/tooling version bumps with no control-flow modifications)

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

• Chore/20250918 #271 — Prior pnpm bump across the same workflows and packageManager fields; closely related to this version progression.
• Chore/20250723 #195 — Similar pnpm version updates in workflows and manifests; related tooling/version changes.
• Chore/20250528 #147 — Earlier CI/packageManager pnpm upgrade in the same files; same class of changes.

Suggested labels

dependencies

Suggested reviewers

• gerardhros

Poem

I twitch my whiskers, hop with glee,
New pins aligned across the tree.
Docs and apps refreshed just so,
pnpm hops to one-one-eight-three—go!
Carrot builds snug, the tests agree. 🥕🐇

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title Check	❓ Inconclusive	The title “Chore/20251014” is too generic and does not convey any meaningful information about the dependency version bumps or workflow updates made in this PR, so it fails to summarize the main changes.	Please update the title to briefly describe the primary change, for example “Bump pnpm and dependency versions across workflows and packages” so readers can quickly understand the focus of the PR.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/20251014

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.07%. Comparing base (3d11228) to head (78e376a).
⚠️ Report is 9 commits behind head on development.

Additional details and impacted files

@@             Coverage Diff              @@
##           development     #299   +/-   ##
============================================
  Coverage        93.07%   93.07%           
============================================
  Files               81       81           
  Lines            13125    13125           
  Branches          1327     1327           
============================================
  Hits             12216    12216           
  Misses             907      907           
  Partials             2        2           

Flag	Coverage Δ
fdm-calculator	94.65% <ø> (ø)
fdm-core	91.93% <ø> (ø)
fdm-data	94.40% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[coderabbitai]

Actionable comments posted: 0

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

fdm-app/package.json (1)

79-79: Move vite-node to devDependencies

vite-node isn’t imported by any runtime code; move it to devDependencies to avoid shipping it in production installs.

   "dependencies": {
-    "vite-node": "^3.2.4",
   },
   "devDependencies": {
+    "vite-node": "^3.2.4",
   }

🧹 Nitpick comments (1)

fdm-docs/package.json (1)

22-25: Align Docusaurus version pinning for consistency

Other Docusaurus packages are pinned to 3.9.1 while @docusaurus/faster uses a caret. Consider pinning it to 3.9.1 to avoid unexpected minor bumps. If you prefer caret here, note the rationale.

Also applies to: 33-35

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3d11228 and 195b0fe.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (11)

• .github/workflows/deploy-docs-test.yml (1 hunks)
• .github/workflows/deploy-docs.yml (1 hunks)
• .github/workflows/release.yml (1 hunks)
• .github/workflows/tests.yml (3 hunks)
• fdm-app/package.json (3 hunks)
• fdm-calculator/package.json (1 hunks)
• fdm-core/package.json (2 hunks)
• fdm-data/package.json (1 hunks)
• fdm-docs/package.json (2 hunks)
• package.json (1 hunks)
• pnpm-workspace.yaml (1 hunks)

🧰 Additional context used

🧠 Learnings (2)

📚 Learning: 2025-05-28T07:57:19.217Z

Learnt from: SvenVw
PR: SvenVw/fdm#147
File: fdm-docs/package.json:39-39
Timestamp: 2025-05-28T07:57:19.217Z
Learning: In pnpm workspaces, the syntax `"typescript": "catalog:"` is valid and correct. It references the version defined in the workspace's catalog section in pnpm-workspace.yaml, allowing consistent dependency versions across packages in a monorepo. The catalog: syntax without a package name is the shorthand for referencing the default catalog.

Applied to files:

• pnpm-workspace.yaml
• fdm-calculator/package.json

📚 Learning: 2025-05-28T07:57:19.217Z

Learnt from: SvenVw
PR: SvenVw/fdm#147
File: fdm-docs/package.json:39-39
Timestamp: 2025-05-28T07:57:19.217Z
Learning: In pnpm workspaces, the syntax `"typescript": "catalog:"` is valid and correct. It references the version defined in the workspace's catalog section in pnpm-workspace.yaml, allowing consistent dependency versions across packages in a monorepo.

Applied to files:

• fdm-calculator/package.json

🔇 Additional comments (6)

fdm-docs/package.json (3)

56-56: pnpm toolchain bump LGTM

---

38-38: typedoc-plugin-markdown v4.9.0 compatibility: v4.9.0 supports TypeDoc 0.28.x.

---

29-30: React 19 support confirmed in Docusaurus v3.9.x
Peer ranges (^18.0.0 || ^19.0.0) in Docusaurus and @docusaurus/faster cover React 19, so no compatibility issues remain.

fdm-app/package.json (2)

109-109: pnpm toolchain bump LGTM

---

61-69: React 19 upgrade: ensure build and peer compatibility

• Install workspace deps: pnpm install, then pnpm --filter fdm-app install
• Confirm pnpm --filter fdm-app run typecheck and pnpm --filter fdm-app run build succeed
• Verify peer ranges for @react-email/components, react-day-picker, react-map-gl, @sentry/react-router, remix-utils, remix-toast, and @react-router/*

pnpm-workspace.yaml (1)

9-24: Catalog version bumps look good

No issues spotted. After merge, run:

pnpm install --frozen-lockfile=false 2>&1 | rg -ni "peer dep warning|unmet peer" || true

to surface any peer dependency warnings across the workspace.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 195b0fe and 78e376a.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (2)

• fdm-app/package.json (2 hunks)
• fdm-docs/package.json (2 hunks)