chore(deps): Move apps/mobile @types/react to the catalog (~19.3.0) #139

Merged

renovate merged 1 commit from renovate/development into main 2026-09-10 20:16:11 +00:00

Conversation 0 Commits 1 Files changed 3 +378 -378

renovate commented 2026-09-09 21:03:55 +00:00

Collaborator

Copy link

Rebased on main and reworked.

apps/mobile was the only manifest that hardcoded @types/react. Renovate bumped that pin to ~19.3.0 and left the catalog on ^19.2.17, so the workspace held two @types/react versions at once.

@types/react is an optional peer, so pnpm forks every package that peers on it. react-i18next split in two: the root importer resolved the 19.3.0 context, packages/i18n the 19.2.18 one (it declares react-i18next as a peer only, so pnpm auto-installs it and resolves it separately). initI18nClient() registered initReactI18next on one copy while the app components read the other, which held no i18n instance. Both apps rendered raw translation keys (saveToJournal, profiles.fastbike, heroTitle) and 37 e2e tests failed on missing English text.

pnpm dedupe cannot merge this — dedupe --check exits clean on the old branch. The two ranges are separate resolution units, and dedupe will not raise the catalog's locked 19.2.18 to satisfy a sibling pin. Renovate's postUpgradeTasks dedupe did run; it changed nothing.

Change

• apps/mobile/package.json — @types/react moves to catalog:
• pnpm-workspace.yaml — catalog @types/react goes to ^19.3.0
• lockfile regenerated: one @types/react@19.3.0, one react-i18next instance, both importers sharing it

No other package version moves; the rest of the lockfile diff is the peer-hash rewrite.

🤖 Generated with Claude Code

Rebased on main and reworked. `apps/mobile` was the only manifest that hardcoded `@types/react`. Renovate bumped that pin to `~19.3.0` and left the catalog on `^19.2.17`, so the workspace held two `@types/react` versions at once. `@types/react` is an optional peer, so pnpm forks every package that peers on it. `react-i18next` split in two: the root importer resolved the 19.3.0 context, `packages/i18n` the 19.2.18 one (it declares react-i18next as a peer only, so pnpm auto-installs it and resolves it separately). `initI18nClient()` registered `initReactI18next` on one copy while the app components read the other, which held no i18n instance. Both apps rendered raw translation keys (`saveToJournal`, `profiles.fastbike`, `heroTitle`) and 37 e2e tests failed on missing English text. `pnpm dedupe` cannot merge this — `dedupe --check` exits clean on the old branch. The two ranges are separate resolution units, and dedupe will not raise the catalog's locked 19.2.18 to satisfy a sibling pin. Renovate's `postUpgradeTasks` dedupe did run; it changed nothing. ## Change - `apps/mobile/package.json` — `@types/react` moves to `catalog:` - `pnpm-workspace.yaml` — catalog `@types/react` goes to `^19.3.0` - lockfile regenerated: one `@types/react@19.3.0`, one `react-i18next` instance, both importers sharing it No other package version moves; the rest of the lockfile diff is the peer-hash rewrite. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

renovate added the

dependencies

label 2026-09-09 21:03:55 +00:00

renovate added 1 commit 2026-09-09 21:03:55 +00:00

chore(deps): Update development to ~19.3.0 ebf5233b9e

renovate scheduled this pull request to auto merge when all checks succeed 2026-09-09 21:03:56 +00:00

ullrich force-pushed renovate/development from ebf5233b9e to 39e2dbf9ad 2026-09-10 19:56:51 +00:00 Compare

ullrich changed title from chore(deps): Update development to ~19.3.0 to chore(deps): Move apps/mobile @types/react to the catalog (~19.3.0) 2026-09-10 19:57:11 +00:00

renovate merged commit 609697eb52 into main 2026-09-10 20:16:11 +00:00

renovate deleted branch renovate/development 2026-09-10 20:16:11 +00:00

renovate referenced this pull request from a commit 2026-09-10 20:16:13 +00:00

chore(deps): Update development to ~19.3.0 (#139)

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels   

dependencies

Dependency updates raised by Renovate (renovate.json5 labels)

  

major

Major version bump — always needs human review, never auto-merged

  

security-pin

Touches a pnpm.overrides CVE remediation pin, not an ordinary dependency

No labels

dependencies

major

security-pin

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

2 participants

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

trails-cool/trails!139

No description provided.