Versioning¶
Two identifiers stay distinct.
| Identifier | What it is | Public status |
|---|---|---|
eve-iac/v1 |
HTTPS API (/api/v1, OpenAPI + semantics) |
Not published. Valid v1 calls may still change until a public cut. |
Product X.Y.Z |
Coordinated package version from VERSION (X.Y.Z-R) |
GitLab Package Registry / Release on tags. Not public indexes. |
VERSION is Debian-style X.Y.Z-R (currently 0.9.0-1 in the repo-root file).
Git tag correspondence¶
The product git tag is always v + the VERSION file. GitLab Release, generic Package Registry paths, and the agent .deb filename use that same string. CI refuses to publish if $CI_COMMIT_TAG is not v0.9.0-1.
| What | This tree |
|---|---|
VERSION |
0.9.0-1 |
| git tag / GitLab Release | v0.9.0-1 |
Debian eve-iac-agent, GET /api/v1/health |
0.9.0-1 |
Python eve-iac, npm @eve-iac/sdk, VSIX, CLI --version, Go tarball |
0.9.0 |
| Go module path | github.com/eve-iac/eve-iac/sdk/go (Release tarball + replace; no public proxy tag) |
| Artifact names | eve-iac-agent_0.9.0-1_amd64.deb, eve-iac-client-0.9.0.vsix, eve_iac-0.9.0-py3-none-any.whl |
| CI toolchain image | ci/image/VERSION (vN, currently independent of product). See GitLab CI. |
Do not treat 0.9.0 as “API v1 is released”. Do not create a product tag while VERSION still holds an older revision.
Agent and clients of the same product line belong together. Platforms, feature floors, and what is not certified: compatibility.