@trackunit/react-components (from 3.0.1) removes CopyableText, and @trackunit/react-table-base-components (from 2.8.1, a minor release) removes CopyableCell, with no compatibility shim — if any of your code imports either, bumping the dependency without running the migration is a compile failure, not a deprecation warning. Repos that never used them are unaffected.

Updated 2026-10-07: corrected the versions (this entry previously said 3.0.0 for both packages) and the CopyableCell migration, which now produces CopyableValue from @trackunit/react-table-base-components 2.12.1.

Run these two commands in the consuming repo after bumping the dependencies:

nx g @trackunit/migrations:migrate
nx g @trackunit/migrations:run-migrations

@trackunit/css-class-variance-utilities (from 2.0.0) has upgraded to the upstream cva@1.0.0-beta.8 package. cvaMerge is removed with no compatibility shim — if any of your code calls it, bumping this dependency without running the migration is a compile failure, not a deprecation warning. Repos that never called cvaMerge are unaffected.

Run these two commands in the consuming repo after bumping the dependency:

nx g @trackunit/migrations:migrate
nx g @trackunit/migrations:run-migrations

Your app can now request four new manifest scopes to check an account's connections and partnerships through the public GraphQL API: connection.view, connection.manage, partner.view, and partner.manage.

New Iris App workspaces now scaffold a databricks-unity-catalog skill under .agents/skills/, alongside the existing graphql, create-app, and other skills. It guides Claude, Cursor, and other coding agents through building a SERVERSIDE_API_EXTENSION that reads or writes customer-uploaded or app-owned tables in your IrisX Analytics Unity Catalog workspace — for data that Trackunit's GraphQL API can't serve.

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.

Your extensions can now describe their own pages to Trackunit Manager's AI assistant. Add an aiNavigation field to a manifest — a list of in-app routes, each with a path, a title, and a description — and the assistant can take a user straight to the page inside your app that answers their question instead of dropping them on its root.

This works today for every extension type that has a page a user can land on: Fleet, Admin, App Settings, Asset Home, Site Home, Customer Home, and Asset Events Actions. The field is opt-in and purely additive — apps that don't declare it behave exactly as before.

See Extension Point Types — AI navigation for the full reference: the manifest shape, both Tanstack Router styles, and in-app paths for entity-scoped extensions.

Manager is moving content inset for Asset Home, Site Home, and Admin extension iframes onto each app. After you upgrade @trackunit/iris-app to 2.5.13 or later, the host stops applying its transitional 1rem inset. Your extension must pad itself with p-content-space on the scrollable content region (or intentionally stay edge-to-edge).

Run the automated migration before or as part of that SDK upgrade — not as optional cleanup afterward. It ships as v2-5-12-p-content-space-codemod in @trackunit/iris-app 2.5.13.

npx nx g @trackunit/migrations:migrate
npx nx g @trackunit/migrations:run-migrations

@trackunit/react-drawer has been reworked to align with Sheet and Modal: a new useDrawer hook owns state and dismiss, a new DrawerHeader component provides the standard toolbar, and the panel now has explicit variant="default" | "modal" semantics. Legacy inline props on <Drawer /> (open, onClose, onOpen, hasOverlay, keepMountedWhenClosed) and the DrawerToggle component have been removed.

You can now inspect serverside function logs for your IrisX Apps directly in the Developer Console.

Open an app that includes Serverside API Extensions, select the Logs tab, then filter by date range and verbosity, search by message or function name, follow live entries when the range includes now, and open any row for full details.

See Viewing serverside function logs for the full guide.

@trackunit/react-components's MenuList claimed Up/Down keyboard navigation and nested-menu support in its docs that it never actually implemented — it was just a role="list" div with click handlers. It's now been rewritten with real WAI-ARIA menu semantics and renamed to MenuContent to reflect that. MenuItem also gains a new submenu prop for building nested menus, and the MenuTree/useMenuTree tree-coordination primitive that powers it is now public API.

This shipped in @trackunit/react-components 2.6.4, a minor release, so a ^2.x range picks up the rename without an explicit major bump.

Updated 2026-10-28: added the version, and renamed the migration to v2-6-0-menulist-rename-to-menucontent to match the release that removed MenuList (it was previously keyed v3-0-0-…).