Releases and versioning¶
The project follows Semantic Versioning (MAJOR.MINOR.PATCH), and has not
reached 1.0.0 yet: no release has been validated in production.
| Part | Meaning |
|---|---|
MAJOR |
An incompatible change: the YAML contract, the DNS answers, or the removal of an /api/v1 route. |
MINOR |
A feature, backward compatible: a new optional YAML key, a new route, a new page. |
PATCH |
A correction with no schema and no configuration change. |
Until 1.0.0¶
0.<lot>.<release>: the minor number is the work package (the "lot" of the
project notes), the patch counts the releases inside it. 0.9.2 is therefore
lot 9, second release. 1.0.0 is reserved for the first release validated in
production — the deployment gate, not a date.
That rule is why the 0.x line can run to 0.10.0, 0.11.0: a minor number is
not a statement of maturity, and 1.0.0 must stay meaningful.
Tags and images¶
- A release is the annotated tag
v<version>, nothing else. No suffix, no-rcfor the lab: the lab runs the same tag as the release. - The
release:*jobs of.gitlab-ci.ymlpublish$CI_COMMIT_TAGas the image tag, sov0.10.0producesgslb:0.10.0,gslb-api:0.10.0,gslb-web:0.10.0. gslb.__version__is the single source; the API imports it, the DNS publishes it inheartbeatand in the snapshot, andtests/test_version.pychecks thatweb/package.jsonagrees.
The API is versioned separately¶
/api/v1/* follows its own number: a product MAJOR does not bump the API, and
a breaking route change moves to /api/v2 while /api/v1 stays available for
the announced transition period. The product version and the API version answer
different questions.
History¶
The first releases numbered the major after the work package (lot 4 → 4.0.0),
which read as seven major versions for a product never deployed. On 2026-11-18
every tag was renamed to the 0.x form, pointing at the same commit. The old names
are gone from the repository; this table is the bridge.
| Tag | Was | Date | Content |
|---|---|---|---|
v0.1.0 |
v1.0.0-lot1 |
2026-11-12 | Lot 1: authoritative DNS, health probes, Docker |
v0.2.0 |
v2.0.0-lot2 |
2026-11-12 | Lot 2: API, console, statistics, learning |
v0.3.0 |
v3.0.0-lot3 |
2026-11-13 | Lot 3: AAAA, typed probes, multi-zone, HA |
v0.3.1 |
v3.1.0 |
2026-11-13 | Lot 3.1: multi-bind VIP, Instances page, user guide |
v0.4.0 |
v3.2.0 |
2026-11-14 | Lot 4: licence, documentation site, release jobs |
v0.4.1 |
v4.0.0 |
2026-11-14 | Lot 4: Debian appliance (qcow2, OVA) |
v0.5.0 |
v5.0.0 |
2026-11-15 | Lot 5: capacity, 10 000 q/s per process |
v0.6.0 |
v6.0.0 |
2026-11-15 | Lot 6: several workers per node |
v0.7.0 |
v6.1.0 |
2026-11-16 | Lot 7: journal at speed, TCP backlog, two-node cluster |
v0.7.1 |
v6.1.1 |
2026-11-16 | Lot 7.1: keepalived check as a file, heartbeat.<zone> |
v0.7.2 |
v6.1.2 |
2026-11-17 | Lot 7.2: keepalived example fixes |
v0.7.3 |
v6.1.3 |
2026-11-17 | Lot 7.3: release jobs that could not run |
v0.7.4 |
v6.1.4 |
2026-11-17 | Lot 7.3: signature through the registry API |
v0.7.5 |
v6.1.5 |
2026-11-17 | Lot 7.3: signed images |
v0.8.0 |
v6.2.0 |
2026-11-17 | Lot 8: probe editor and template library |
v0.9.0 |
v7.0.0 |
2026-11-18 | Lot 9: console rewritten on Mantine |
v0.9.1 |
v7.1.0 |
2026-11-18 | Lot 9.1: audit page, read-only token, phone layout |
v0.9.2 |
v7.2.0 |
2026-11-18 | Lot 9.2: Instances page, VIP check, probe links |
v0.10.0 |
— | 2026-11-18 | Lot 10: DNS command line, init/check/routes/probe |
v0.10.1 |
— | 2026-11-19 | Lot 10.1: journal filters and total, clickable notices, zone removal, template impact |
v0.10.2 |
— | 2026-11-19 | Qualified pool key in the Zones answer count |
v0.10.3 |
— | 2026-11-19 | Lot 10.2: the zone filter moves to the Overview |
v0.10.4 |
— | 2026-11-19 | A zone filter that keeps its own liveness rows |
v0.10.5 |
— | 2026-11-19 | Lot 10.3: the time window joins the pages that read it |
v0.10.6 |
— | 2026-11-19 | Lot 10.4: documentation pass, compose tags from GSLB_VERSION |
v0.11.0 |
— | 2026-11-19 | Lot 11 step 1: source address in the history, /metrics, plaintext authentication refused |
v0.11.1 |
— | 2026-11-19 | Lot 11 step 2: a restore script with an integrity check and a SHA proof, make restore-test |
v0.11.2 |
— | 2026-11-19 | Lot 11 step 2 patch: the appliance restore procedure corrected for the read-only API container |
v0.11.3 |
— | 2026-11-19 | Lot 11 step 3: OIDC sign-in, three roles enforced by the API, and a console that only draws what the role allows |
v0.11.4 |
— | 2026-11-19 | The env file reaches the container: every variable the API and the DNS read is declared in the shipped compose files |
v0.12.0 |
— | 2026-11-19 | Lot 11 step 4: a bilingual console (EN/FR), component tests and a Playwright end-to-end suite |
v0.13.0 |
— | 2026-11-20 | Lot 12: the identity provider is configured from the console, with the environment as floor and Entra/Google claim handling |
v0.13.1 |
— | 2026-11-20 | One sign-in selector (SSO, user, token) and a branded, centred sign-in page |
Images already published under an old tag keep that tag in the registry: those artefacts are immutable, and re-signing them would prove nothing. Only the repository tags were renamed.
A clone that still has the old tags must prune them, otherwise a later
git push --tags would resurrect them:
git fetch --prune --prune-tags