chore(deps): bump dependencies across all workspaces - #64
Conversation
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
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
WalkthroughThe 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. ChangesDependency and formatting updates
Estimated code review effort: 2 (Simple) | ~10 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
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. Comment |
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
There was a problem hiding this comment.
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
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (13)
apps/api/package.jsonapps/docs/package.jsonapps/docs/scripts/sync-changelog.tsapps/style/package.jsonapps/style/src/components/sidebar/_index.scssapps/style/src/components/sidebar/_theme-switcher.scsspackage.jsonpackages/ui/package.jsonpnpm-workspace.yamltooling/cspell/package.jsontooling/eslint/package.jsontooling/prettier/package.jsontooling/tailwind/package.json
Ran
tazerecursively over every workspace and both pnpm catalogs, using the repo's owntaze.config.ts.What moved
catalog:(default)@eslint/js,@tailwindcss/postcss,@types/node,cspell,eslint,prettier,tailwindcsscatalogs.react19@types/react,react,react-dom@changesets/cli,@commitlint/*,@turbo/gen,lefthook,taze,turbo,packageManager→pnpm@11.17.0@repo/apilightningcss-wasm,shadcn,browserslist,postcss@repo/docsnext/@next/*,ai/@ai-sdk/*,shiki/@shikijs/*,@takumi-rs/*,mermaid,motion,lucide-react,import-in-the-middle,swiper,twoslash@repo/stylelightningcss,browserslist,ora,postcss@repo/uiradix-ui+@radix-ui/*,@vidstack/react,lucide-react,motiontooling/*typescript-eslint,eslint-plugin-turbo,@next/eslint-plugin-next,@cspell/*,prettier-plugin-tailwindcss,postcssTwo deliberate holds
TypeScript stays on 6.x
tazeoffers 7.0.2 andtaze.config.tsexplicitly permits typescript majors (packageMode: { typescript: 'major' }), but:That kills all seven lint tasks. Held at
^6.0.3, with a comment inpnpm-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. Build —
fumadocs-ui16.13.0 droppeduseTranslations(andI18nLabel) fromcontexts/i18n, a breaking change in a minor release. Everyfumadocs-openapi10.x still imports it:Nothing flagged it at install time —
fumadocs-openapi@10.10.3declares a peer offumadocs-ui ^16.9.0, which 16.13.0 satisfies. The peer range is stale upstream.2. Docs lint — pinning just
core+uifixed the build but left:That query string is
fumadocs-mdx's loader contract, whichfumadocs-coreconsumes.fumadocs-mdx15.2.0 emits a shapefumadocs-core16.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
devalready 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-openapi11.x, which requiresfumadocs-ui ^16.10.0and 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 ondev; needed forpnpm formatto 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), andpnpm lintfor all six non-docs packages.For
@repo/docs,bun ./scripts/lint.tsnow passes (collected 14 URLs, 0 errors) and eslint reduces to the same 14no-unsafe-*errors a cleandevcheckout produces without a prior build — CI resolves those by runningpnpm buildfirst. The Vercel web preview built successfully on the previous commit, confirming the build fix.Summary by CodeRabbit
Chores
Refactor