In this version we upgraded the foundation for our tailwind to use tailwind 4.1.18 instead of 3.x.

Effected packages:

• @trackunit/css-core - contains the generated css file to use
• @trackunit/css-tailwind - deprecated, just remove it from your package.json
• @trackunit/css-tailwind-custom-properties-plugin - deprecated, just remove it from your package.json

Also, many of the React libraries have changed, so make sure to update all Trackunit dependencies.

Use this command to make sure you are updated with all latest Trackunit dependencies

npx npm-check-updates "/@trackunit/" -u

Now you need to install the latest tailwind dependencies

npm install @tailwind/postcss@4.1.18 --save-dev
npm install tailwindcss@4.1.18 --save-dev

After this the 'serve' command will use the correct tailwindcss/postcss and all Trackunit dependencies are updated.

For more information on how it might effect your own tailwind classes in your codebase - check this Migration guide

Released stable version v2 of Assets API.

The Assets API v2 builds on the foundation of v1 with expanded querying, improved asset lifecycle management, and enhanced flexibility. In addition to onboarding, offboarding, and updating asset specifications, v2 introduces advanced filtering and pagination, asset querying by multiple identifier types, asset hiding and unhiding, and dedicated support for asset notes. The API also streamlines telematics device attachment flow, providing a more consistent and scalable way to manage assets across accounts and fleets. For more information, see the updated endpoint documentation.

Below a list of all available endpoints:

➕ GET: /asset/v2/assets

Get assets

➕ GET: /asset/v2/assets/{assetId}

Get asset

➕ POST: /asset/v2/assets

Create assets

➕ PATCH: /asset/v2/assets

Update assets

➕ DELETE: /asset/v2/assets/{assetId}

Delete asset

➕ POST: /asset/v2/assets/query

Query assets by identifiers

➕ PATCH: /asset/v2/assets/hidden

Hide or unhide assets

➕ PATCH: /asset/v2/assets/note

Update asset note

➕ POST: /asset/v2/assets/notes/query

Fetch asset notes

➕ POST: /asset/v2/assets/{assetId}/telematics-devices

Attach telematics device

In this version of the App SDK, we have upgraded Node to the current LTS version 24.11.1. Make sure to upgrade your workspace to at least that version.

If using volta, you can install the latest LTS version of Node by running:

volta install node@lts

or by adding the following to your root package.json

"volta": {
  "node": "24.11.1"
}

Otherwise, you can download the latest LTS version of Node from the Node.js website.

Filter URL Synchronization​

Filter states are now automatically synchronized with URL parameters, allowing users to bookmark or share filtered views. When filters are applied, the URL updates to reflect the current filter state, and the filters are restored when navigating back to that URL.

Breaking Change​

TanStack Router is now required for Iris app extensions using the filter bar.

Your app entry point must be wrapped with TanStack Router's RouterProvider. See the iris-app-with-router-example for a complete implementation example showing how to set up the router in your Iris app extension.

We enhanced the endpoint for setting custom field values to support definition keys as an alternative to definition UUIDs. This improvement eliminates the need to hardcode UUIDs in your integration code, making your implementations more maintainable and readable.

➕ POST: /api/custom-fields/v1/set-values/

Set custom field values

The DayRangePickerPopover component is being deprecated in favor of the new DayRangeSelect component. The new DayRangeSelect component replaces it with all the same functionality but with a more user friendly user experience.

In this version of our Iris App SDK, we have upgraded NX to v21.1.3. Make sure to upgrade your extensions to the latest version of NX.

npx nx migrate 21.1.3
npx nx migrate --run-migrations

Please refer to Maintaining Your Application for more information.

Released stable version v1 of Bluetooth tag configuration API. For more information, see the documentation and introduction of the endpoints.

Below is a list of all available REST endpoints:

KIN Challenge​

➕ POST: /v1/kin-challenge/sign

Sign KIN Challenge

Utilization Profiles​

➕ POST: /v1/utilization-profiles/search

Search Utilization Profiles

➕ GET: /v1/utilization-profiles/{profileId}

Get Utilization Profile

➕ PUT: /v1/utilization-profiles/{profileId}/acknowledge-desired/{deviceId}

Acknowledge Desired Utilization Profile

➕ PUT: /v1/utilization-profiles/{profileId}/acknowledge-reported/{deviceId}

Acknowledge Reported Utilization Profile

Released asset clustering in the GraphQL API.

The new assetClusters field supports obtaining clusters of assets based on their current location. Useful for drawing a map of clusters of assets.

It accepts the same AssetFiltersInput as the assets search field, so they can easily be combined if needed.

➕ GQL: Query.assetClusters

See all relevant GQL documentation

Released beta version v1beta1 of Fleet Data Health API. For more information, see the documentation and introduction of the endpoints.

Below is a list of all available REST endpoints:

Issue API​

➕ GET: /v1beta1/assets/{assetId}/issues

Get issues by asset

➕ GET: /v1beta1/issues

Get issues

➕ GET: /v1beta1/issues/{issueId}

Get issues