Skip to content

chore(deps): bump dependencies across all workspaces - #64

Merged
techwithanirudh merged 3 commits into
devfrom
chore/bump-dependencies
Jul 31, 2026
Merged

chore(deps): bump dependencies across all workspaces#64
techwithanirudh merged 3 commits into
devfrom
chore/bump-dependencies

Conversation

@techwithanirudh

@techwithanirudh techwithanirudh commented Jul 31, 2026

Copy link
Copy Markdown
Owner

Ran taze recursively over every workspace and both pnpm catalogs, using the repo's own taze.config.ts.

What moved

Scope Updates
catalog: (default) @eslint/js, @tailwindcss/postcss, @types/node, cspell, eslint, prettier, tailwindcss
catalogs.react19 @types/react, react, react-dom
root @changesets/cli, @commitlint/*, @turbo/gen, lefthook, taze, turbo, packageManagerpnpm@11.17.0
@repo/api lightningcss-wasm, shadcn, browserslist, postcss
@repo/docs next/@next/*, ai/@ai-sdk/*, shiki/@shikijs/*, @takumi-rs/*, mermaid, motion, lucide-react, import-in-the-middle, swiper, twoslash
@repo/style lightningcss, browserslist, ora, postcss
@repo/ui radix-ui + @radix-ui/*, @vidstack/react, lucide-react, motion
tooling/* typescript-eslint, eslint-plugin-turbo, @next/eslint-plugin-next, @cspell/*, prettier-plugin-tailwindcss, postcss

Two deliberate holds

TypeScript stays on 6.x

taze offers 7.0.2 and taze.config.ts explicitly permits typescript majors (packageMode: { typescript: 'major' }), but:

Error: typescript-eslint does not support TS 7.0.
    at typescript-eslint@8.65.0/dist/index.js:52:11

That kills all seven lint tasks. Held at ^6.0.3, with a comment in pnpm-workspace.yaml. Revisit when typescript-eslint supports TS 7.

The fumadocs family stays on its current versions

Two separate failures, both from version skew inside the family:

1. Buildfumadocs-ui 16.13.0 dropped useTranslations (and I18nLabel) from contexts/i18n, a breaking change in a minor release. Every fumadocs-openapi 10.x still imports it:

Export useTranslations doesn't exist in target module
  fumadocs-openapi/dist/ui/client/i18n.js:4
Did you mean to import useI18n?

Nothing flagged it at install time — fumadocs-openapi@10.10.3 declares a peer of fumadocs-ui ^16.9.0, which 16.13.0 satisfies. The peer range is stale upstream.

2. Docs lint — pinning just core + ui fixed the build but left:

SyntaxError: Export named 'frontmatter' not found in module
  '.../development/apps/docs.mdx?collection=docs&only=frontmatter'

That query string is fumadocs-mdx's loader contract, which fumadocs-core consumes. fumadocs-mdx 15.2.0 emits a shape fumadocs-core 16.9.0 doesn't read, so those two have to move together too.

Bumping the family piecemeal just relocates the failure, so all nine packages now sit on the versions dev already runs. Pinned exactly, not with carets — every caret here floats straight back into the incompatible range (^16.9.0 → 16.13.0, ^15.0.7 → 15.2.0).

Upgrading the family as a coordinated set — including fumadocs-openapi 11.x, which requires fumadocs-ui ^16.10.0 and restructures its UI entrypoints — is worth doing, but as its own PR rather than inside a routine bump.

Incidental formatting

  • apps/docs/scripts/sync-changelog.ts — prettier 3.9 lays out an arrow function with a return-type annotation differently.
  • apps/style/src/components/sidebar/_index.scss, _theme-switcher.scss — already unformatted on dev; needed for pnpm format to pass. Same change appears in fix(docs): keep APP_PORT numeric in dynamic-config installer #63, whichever lands first.

Verification

Green locally: pnpm format, pnpm check:spelling, pnpm lint:ws (sherif), and pnpm lint for all six non-docs packages.

For @repo/docs, bun ./scripts/lint.ts now passes (collected 14 URLs, 0 errors) and eslint reduces to the same 14 no-unsafe-* errors a clean dev checkout produces without a prior build — CI resolves those by running pnpm build first. The Vercel web preview built successfully on the previous commit, confirming the build fix.

Summary by CodeRabbit

  • Chores

    • Updated development, runtime, UI, styling, documentation, and linting packages.
    • Updated workspace tooling and package manager requirements.
    • Refreshed spelling, formatting, Tailwind, and build-related tools.
  • Refactor

    • Simplified internal changelog synchronization code without changing behavior.
    • Reformatted sidebar and theme-switcher styles with no visual changes.

Ran taze recursively over every workspace and the pnpm catalogs.

TypeScript is deliberately held at ^6.0.3. taze offers 7.0.2 (the repo's
taze config allows typescript majors), but typescript-eslint 8.x refuses
to load against it - "typescript-eslint does not support TS 7.0" - which
fails every lint task in the repo. Noted inline in pnpm-workspace.yaml so
the next person does not have to rediscover it.

Also reformats two files that prettier 3.9 lays out differently, and two
sidebar partials that were already unformatted on dev.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013xR9ywD6vmwcbAce4VXfbz
@vercel

vercel Bot commented Jul 31, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
coolify-tweaks-web Ready Ready Preview Jul 31, 2026 6:16am
1 Skipped Deployment
Project Deployment Actions Updated (UTC)
coolify-tweaks-api Ignored Ignored Preview Jul 31, 2026 6:16am

@coderabbitai

coderabbitai Bot commented Jul 31, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Walkthrough

The change updates dependency versions across workspace, application, UI, and tooling packages. It also updates the required pnpm version and reformats selected TypeScript and SCSS code without changing runtime behavior.

Changes

Dependency and formatting updates

Layer / File(s) Summary
Workspace and package manager versions
package.json, pnpm-workspace.yaml
Root tooling, pnpm, and shared catalog versions are updated. TypeScript 7 compatibility comments are added.
Application and UI dependency versions
apps/api/package.json, apps/docs/package.json, apps/style/package.json, packages/ui/package.json
Application and UI dependency constraints are updated. Several documentation dependencies are pinned to exact versions.
Development tooling dependency versions
tooling/*/package.json
CSpell, ESLint, Prettier, and Tailwind dependency versions are updated.
Source formatting cleanup
apps/docs/scripts/sync-changelog.ts, apps/style/src/components/sidebar/*.scss
The MDX callback and SCSS selectors and declarations are reformatted without changing behavior.

Estimated code review effort: 2 (Simple) | ~10 minutes

Poem

A rabbit checks the versions bright,
Updates tools from morn to night.
SCSS hops into cleaner lines,
MDX neatly realigns.
No behavior changed—just tidy code,
Then off I bound along the road.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely summarizes the primary change: dependency updates across the repository workspaces.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/bump-dependencies

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

Comment @coderabbitai help to get the list of available commands.

fumadocs-ui 16.13.0 dropped the useTranslations export from
fumadocs-ui/contexts/i18n, but every fumadocs-openapi 10.x still imports
it, so the docs build failed:

    Export useTranslations doesn't exist in target module
    fumadocs-openapi/dist/ui/client/i18n.js:4

fumadocs-openapi 10.10.3 declares a peer of fumadocs-ui ^16.9.0, so
nothing flagged this at install time - the peer range is stale upstream.

Pinned exactly rather than with a caret, since ^16.9.0 resolves straight
back to 16.13.0. Every other fumadocs package in the tree accepts
fumadocs-core ^16.7.x, so they stay on their bumped versions.

Moving forward instead would mean fumadocs-openapi 11.x, which requires
fumadocs-ui ^16.10.0 and restructures its UI entrypoints - worth doing,
but as its own PR rather than inside a routine dependency bump.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013xR9ywD6vmwcbAce4VXfbz
Pinning only fumadocs-core and fumadocs-ui fixed the build but left the
docs lint script failing:

    SyntaxError: Export named 'frontmatter' not found in module
    '.../development/apps/docs.mdx?collection=docs&only=frontmatter'

That query is fumadocs-mdx's loader contract, which fumadocs-core
consumes. fumadocs-mdx 15.2.0 emits a shape that fumadocs-core 16.9.0
does not read, so the two have to move together.

These packages are coupled tightly enough that bumping them piecemeal
just moves the failure around, so the whole family now sits on the
versions dev already runs. Pinned exactly, since every caret here floats
back into the incompatible range.

With this, bun ./scripts/lint.ts passes and @repo/docs lint reduces to
the same 14 no-unsafe-* errors a clean dev checkout produces without a
prior build - which CI resolves by running pnpm build first.

Upgrading the family as a set is worth its own PR.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013xR9ywD6vmwcbAce4VXfbz

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@package.json`:
- Line 61: Regenerate pnpm-lock.yaml using pnpm@11.17.0 so it includes the
catalog and importer entries declared in package.json, and add a CI
dependency-install step before any pnpm commands. Ensure CI uses the declared
package manager and frozen installs succeed.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 42c13187-9eb3-4f75-8ba5-8e728d08c2ca

📥 Commits

Reviewing files that changed from the base of the PR and between fb6cc9b and 7ffc789.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (13)
  • apps/api/package.json
  • apps/docs/package.json
  • apps/docs/scripts/sync-changelog.ts
  • apps/style/package.json
  • apps/style/src/components/sidebar/_index.scss
  • apps/style/src/components/sidebar/_theme-switcher.scss
  • package.json
  • packages/ui/package.json
  • pnpm-workspace.yaml
  • tooling/cspell/package.json
  • tooling/eslint/package.json
  • tooling/prettier/package.json
  • tooling/tailwind/package.json

Comment thread package.json
@techwithanirudh
techwithanirudh merged commit d4a3eea into dev Jul 31, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants