Changed
- Packaging only — no user-visible change.
AIS Tracing overview
beta22 releases
AIS Tracing release notes
Every released version of AIS Tracing, newest first, with what changed in it — written at the moment the release was cut, not reconstructed afterwards.
Follow a single value — a correlation id, an order reference — through every container of an Azure Cosmos DB account, and see where it got to. Samples your containers, works out which field links documents together, then draws each step on a timeline. Empty rows matter as much as full ones: they show where the data hasn't arrived.
Current version
Version 0.1.27, released 28 September 2026. This is what the download buttons below install.
Changed
- Packaging only — no user-visible change.
Free for personal, educational and non-profit use. Commercial use — including a solo consultant on client work — requires a licence. Every build is produced by release CI and served from mayorana.ch.
All versions
Changed
- Packaging only — no user-visible change.
Added
- A banner at startup for occasional messages from us, such as a request for feedback. It is fetched once from mayorana.ch, stays until you dismiss it and is not shown again after that. If the notice cannot be fetched, no banner appears and startup is not slowed. Setting
DISABLE_UPDATE_CHECKturns it off along with the update check.
Changed
- Packaging only — no user-visible change in the app. The notes for every release, with its download, are now published at mayorana.ch/en/apps/ais-tracing/releases.
Changed
- Error handling and feedback across the scan, trace and account screens: a failure says what failed and what to do about it, instead of leaving a view empty.
- Long lane names are truncated cleanly rather than pushing the timeline out of shape.
Fixed
- The Windows build script handles cross-compilation correctly, and CI now blocks on clippy warnings.
Changed
- CI pipeline only — no user-visible change.
Fixed
- "AIS Tracing" is capitalised the same way in the window title and the in-app headers.
Changed
- The update check sends a versioned User-Agent, which is what makes per-version adoption visible in the download logs — the number that says how many people are still on a build with a bug that is already fixed.
Changed
- Internal: Azure sign-in consolidated into one
start_loginpath shared by every screen that can trigger it.
Added
- Windows support: a signed installer, the Azure CLI installed for you if it is missing, and a Start menu entry.
Added
- The update check resolves the artifact for the platform it is running on, so the banner offers the macOS, Windows or Linux build directly instead of the download page.
Fixed
- Long lane names and field names wrap instead of overflowing their column.
Added
- Scanning a Cosmos DB account reports why it failed: an expired Azure session is named as one, rather than surfacing as an account with no containers.
Changed
- Release safety: the pipeline fails outright when the deploy secrets are missing, rather than reporting success for a release nobody can download.
Changed
- Builds are distributed from mayorana.ch instead of GitHub Releases. Every release publishes a
latest.jsoncarrying thesha256of each artifact, so a download can be verified against a source that does not deliver it. - Licensed under PolyForm Noncommercial 1.0.0: free for personal, educational and non-profit use; commercial use requires a licence.
Fixed
- The macOS binary is signed before packaging and checksummed after, so the published
sha256matches the file you actually download.
Fixed
- The app adopts the login shell's
PATH, soazis found when it is launched from Finder rather than from a terminal.
Fixed
- A release started from the Actions UI tags the version it prepared, instead of the branch it was dispatched from.
Added
- Multi-window support: several traces open side by side, each in its own window.
Fixed
- The release script no longer hangs waiting for a confirmation prompt when it runs without a terminal.
Added
- A lightweight update check at startup, with a banner when a newer build is available. It reads the manifest published beside the builds, so it keeps working regardless of where the source lives.
The same history, as JSON
This page is generated from a feed published beside the builds — the same file AIS Tracing reads when it checks for an update. Point a script at it if you track versions across a team.
https://mayorana.ch/downloads/ais-tracing/latest/releases.jsonNeed it adapted to your work?
Each of these tools is built and maintained by us. If you need a variant — a different data source, your own conventions, a feature your team is missing, an on-prem build — that is the kind of work we take on.
Get in touch