* fix: pin tsx as local devDependency in @plane/i18n
The `generate:types` and `sync:check` scripts used `npx tsx`, which
resolved to `[email protected].0` — a release whose `esbuild@~0.27.0` dependency
is not yet published to the public npm registry (latest available is
0.25.x). This caused local builds to fail with ETARGET.
Add `[email protected].6` (last known-good, uses esbuild@~0.25.0) to the
pnpm workspace catalog and declare it as a devDependency of
`@plane/i18n`, then call `tsx` directly instead of via `npx`.
* ci: run i18n sync check via pnpm workspace tsx
Replace `npx --yes tsx@<pinned>` with a standard pnpm install and
`pnpm --filter=@plane/i18n check:sync`, so the job uses the tsx
version locked in the workspace catalog instead of resolving a fresh
one from npm on every run (which recently broke due to [email protected].0's
unpublished esbuild peer).
Also broaden the path filter to `packages/i18n/**` so changes to the
package manifest or catalog re-trigger the check.
* ci(i18n): run sync-check via pnpm dlx tsx, drop workspace install
The sync-check script only uses Node built-ins plus tsx, so installing
the full @plane/i18n dependency graph (i18next, react, etc.) was
unnecessary. Replace the install + pnpm store cache with a single
pnpm dlx tsx invocation.
---------
Co-authored-by: Prateek Shourya <[email protected]>
