Skip to main content
Status: target. The checklists below describe how an upgrade should run. Encore upgrades are omitted until stackra gen emits the Encore app (0124); add that section with the generator.
Every upgrade is its own pull request, never mixed with feature work, and is merged only when pnpm verify is green. Say in the description what you ran and what you did not.

​
Any upgrade

  1. Read the upstream release notes and list the breaking changes that touch this repo.
  2. Bump the version in one place (see below) and nowhere else. Versions live only in pnpm-workspace.yaml catalogs, mise.toml and packageManager.
  3. pnpm install, then pnpm verify.
  4. Add a changeset for every member whose behaviour or dependencies changed.
  5. If the upgrade changes a rule, update the page that states it in the same pull request, and write an ADR if it reverses a recorded decision.

​
Toolchain: Node, pnpm, gitleaks

  • mise.toml pins the tool; packageManager in package.json must carry the same pnpm version (corepack reads that one). A mismatch is a bug.
  • engines in package.json and .node-version follow the Node pin.
  • apps/mobile/eas.json pins node and pnpm for EAS builds under build.base. Change them in the same pull request.
  • CI installs from mise.toml, so nothing else needs editing (CI).
Checklist: edit mise.toml, packageManager, .node-version, eas.json pins, then mise install && pnpm install && pnpm verify.

​
Catalog dependencies (TypeScript, React, tools)

  • Bump the entry in the right catalog in pnpm-workspace.yaml. The default catalog is for versions shared widely; named catalogs (build, quality, mobile, and so on) group a toolchain by risk and cadence.
  • Check the licence allow-list and the release-age rule in Dependencies first.
  • A major bump of a preset package under packages/tooling/* is verified by every member’s verify; change the preset, never patch each consumer.
  • Run pnpm knip so a removed dependency does not leave dead exports behind.

​
Expo SDK

Expo SDK versions move the whole mobile catalog together. Never bump one package alone.
1

Read the SDK changelog and the React Native release notes

Note removed APIs, the new minimum Node and Xcode, and any New Architecture requirement.
2

Bump the expo version in the mobile catalog

Then run pnpm --filter @figentra/mobile exec expo install --fix to learn the compatible versions of every expo-* and React Native package, and copy those versions into the mobile catalog (strict catalog mode means the catalog is the only place to write them).
3

Check the project

pnpm --filter @figentra/mobile run doctor (that is expo install --check) and npx expo config --type public from apps/mobile.
4

Prove the bundle builds

pnpm --filter @figentra/mobile build (that is expo export for both platforms), then run a development build on a simulator.
5

Treat it as a native change

The runtime version changes, so over-the-air updates cannot reach old builds. Plan a new store build per Mobile release and do not publish an update across the boundary.

​
Licensed UI packages (HeroUI Pro, Uniwind Pro)

Not installed yet. When they are: bump them with the matching free packages in the same catalog, and confirm the licence token is present as a secret in CI and EAS before installing, or a token-less install caches an empty stub (Mobile release).

​
Checks that back this page

See also Renovate, Dependencies and Release.