Outdated `@trackunit/*` dependency warning now points to the migrations generator

If your Iris App build warned you about outdated @trackunit/* dependencies, it used to tell you to reach for npm-check-updates — a command that never actually applied our migrations, leaving you on a path that didn't work. That warning now points at the right tool.

What changed

Updated 2026-10-28: corrected the versions (this entry previously said v2.4.25 and v2.5.26) and removed the claim that new workspaces get an update:trackunit script; they don't.

The outdated-dependency check in @trackunit/iris-app-build-utilities (from v2.4.19) now recommends the @trackunit/migrations generator instead of npm-check-updates:

npm i -D @trackunit/migrations   # only needed once
npx nx g @trackunit/migrations:migrate
npx nx g @trackunit/migrations:run-migrations

migrate updates every @trackunit/* dependency in your package.json and installs them; run-migrations then applies any code migrations those new versions ship.

Workspaces scaffolded with @trackunit/iris-app v2.5.20 or later come with @trackunit/migrations already added as a devDependency, so the command in the warning works immediately. They no longer get an update:trackunit script. If your workspace predates this, add the package once as shown above — an update:trackunit script you already have (for example one calling npm-check-updates from CI) is left as-is, so nothing breaks under you.

See Maintaining Your Application for the full upgrade guide.