Skip to content

chore: centralize rimraf version with pnpm catalog#684

Open
Shinyaigeek wants to merge 1 commit into
thesysdev:mainfrom
Shinyaigeek:chore/catalog-rimraf
Open

chore: centralize rimraf version with pnpm catalog#684
Shinyaigeek wants to merge 1 commit into
thesysdev:mainfrom
Shinyaigeek:chore/catalog-rimraf

Conversation

@Shinyaigeek

Copy link
Copy Markdown
Contributor

What

Centralize the rimraf version through the shared pnpm catalog.

  • Add rimraf: "^5.0.7" to the catalog: in pnpm-workspace.yaml.
  • Reference it via the catalog: protocol from the three workspace packages that use it: react-ui, openui-cli, browser-bundle.

Why

rimraf was declared independently in three packages (all ^5.0.7). Centralizing keeps it aligned in one place, consistent with the other already-centralized deps (react, eslint, typescript, …).

Scope

Following the established convention, only packages/* use the catalog: protocol.

Notes

  • Resolved version is unchanged (5.0.10) — pure centralization, no behavioral impact.
  • Lockfile diff is limited to the catalog entry + the three catalog: specifiers.
  • pnpm install --frozen-lockfile passes.

🤖 Generated with Claude Code

Add rimraf (^5.0.7) to the shared pnpm catalog and reference it via the
catalog: protocol from react-ui, openui-cli, and browser-bundle.

Following the existing convention, only packages/* use catalog:. Resolved
version is unchanged (5.0.10).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.

1 participant