Versions
The history of what was delivered, where each version runs today, and the way to its release notes.
Checked in the application on September 5, 2026
The Deployments screen answers “what runs now”. The Versions screen, in the History menu, answers “what happened”: the history of delivered versions, most recent first, where each one runs today, and the way to what it contained. It is a screen for reading: nothing is deployed there, nothing is deleted.
Who can ViewerProduct ownerDeveloperManagerAdministrator
Every role reads the whole screen; it does nothing but read.
The two modes do not read the same way
What a row shows
| Element | What it is |
|---|---|
| The number and the tag | The number typed at creation (a free string, 2026.07.1 or stable are valid) and the name of the tag actually created, resolved from the workspace pattern. |
| When, who | The creation date and the person. |
| The description | The comment typed at creation, if any. It is not the release notes, which are computed. |
| The environments | In tag mode, one chip per environment where the version runs, with “×3” if it was released there several times. “Never released” otherwise. |
| “partial” | At least one project did not receive its tag. |
| Tags created | The detail per project: the tagged commit, or the error message of the project that refused. |
| “Release notes” | The button to the computed notes, see below. |
An environment deleted since, or a project unlinked since, stay readable on old rows: the names are kept as they were at delivery time, without a link.
Opening the release notes
- From a row
“Release notes” opens the computed notes of this version: what went between the previous deployment and this one. They need a release: on a never-deployed version, the button is greyed out, “Available once the version has been released at least once”. When the version runs on several environments, a menu asks “On which environment?”, because the notes differ depending on the target: the intermediate deployments are not the same on Acceptance and on Production.
- Coming back
The notes have their own address. The back arrow, or the browser’s Back button, brings you here, on the same environment tab.
Browsing the history
The list is paginated at the bottom of the screen, 50 versions per page, adjustable to 100 or 200. Changing page or tab scrolls back to the top. There is neither sorting nor search: within a given sequence, chronological order is the order of versions, and a sort on the number would mislead (1.2.11 before 1.2.7). The environment tab lives in the URL: a shared link opens the right sequence.
When the workspace has no version, the screen says so and points to the right action: “Create a version” in tag mode, from the main branch tile of the Deployments screen; “Go deploy” in branch mode, where versions are born from deployments.