Skip to main content

Version Timeline

The Version Timeline controls which platform version your project runs on. You can move to a newer release when you are ready, or roll back to an older one. You decide when to change versions, so the timing fits your own release schedule.

The Version Timeline is one of the two sections on the System page, found in the TagoIO & API sidebar under System. The page header reads "System"; the card is titled "Version Timeline" with the subtitle "Pick the platform version this project runs." A Refresh button reloads the list.

Reading the timeline​

Versions are listed by date and grouped by where they sit relative to the version you run today:

  • Newer Versions: releases ahead of your current version. A count badge shows how many are available, the most recent one is tagged "Latest", and each row has an Update action to move to it.
  • Current Version: the version your project runs now, tagged "Current".
  • Older Versions: releases behind your current version, each with a Rollback action to return to it.

Each release comes with notes describing what changed, so you can decide when to update or roll back.

Updating and rolling back​

Version changes are manual. There is no automated or scheduled mechanism, so an administrator triggers an Update to move forward or a Rollback to move back. Your team decides when version changes happen.

Before changing versions, keep a current backup so you can recover if an upgrade or rollback surfaces an issue. See the backup documentation.

Components affected by version changes​

Changing versions may affect the following infrastructure components:

  • Admin: administrative user interface and management tools.
  • TagoRUN: the runtime environment that executes project workflows.
  • API: backend APIs that provide data access and integration points.
  • Features (Microservices): the microservices that run specific project functionality.