Versions and projects · Chapter 14
The time line
A reprint from 2023 should look like the original, not like today's CI. So the time line answers at any moment which version applied on a given day.
What the time line shows
At the top of the client's page, under Versions, each version has a card: name, a strip with its colours, the date and a badge.
| Badge | Means |
|---|---|
| current | the version that applies today, with “since” and the date |
| upcoming | published, but applies only from a later day |
| Draft | not published yet; the card is dashed |
Older versions carry “from” and the date they applied from. A click on a card shows that version in every tab.
As of
The date field As of shows the version that applied on the chosen day. If there was none yet, nexbrand says so: “On … there was no published version yet. The first is valid from …”. The button 3 years ago jumps back exactly three years; it shows only when there is a version that old.
When you look at an older version, a hint stands above the tabs, such as “You see version 2022, valid from … to …. The current one is 2026.” To the current one takes you back.
A version that applies later
If you publish a version with a date in the future, say for a relaunch on 1 January, it carries the badge upcoming until then. Whoever opens it reads: “You are looking at version 2027. It is valid from …; until then, 2026 applies.”
- In the app, the code and the API, the previous version applies until that day.
- If there is no previous one, none applies until then.
- Projects stay on their version anyway until somebody moves them.
Which day is “today” depends on the server's time zone, Europe/Berlin out of the box.
From programs
A program asks the same question through the API with ?at=2023-10-04, or over MCP with the field at. So a script builds the reprint with the colours that applied then.
Pavo saysThe history of all versions, with origin and note, is in the tab History. That is also where you compare two versions.