Releases¶

Version format¶

EnforceGate vX releases use the scheme:

<Year>.<Major>.<Minor>[-<Tier>]

Examples:

Example	Meaning
`2026.1.0`	First release of the year 2026.
`2026.2.0 (IR)`	Internal release destined for our engineering team.
`2026.3.0 (EA)`	Early Access release for testing and evaluation.
`2026.6.0 (GD)`	General Deployment release — recommended for production.

<Year> tracks calendar year, not a semver major.
<Major> and <Minor> are numeric and monotonically increasing within the year.
<Tier> is one of GD, ED, SR, EA, IR (see below) and is part of the version string — it flows through to the image tag (enforcegate/standalone:2026.30.0-EA) and to the boot-card "Image version" line.

Release tiers¶

EnforceGate vX releases are categorised as follows:

General Deployment (GD): The most mature and stable release. Recommended for production environments where reliability is critical.
Early Deployment (ED): Incorporates newly added features and the latest bug fixes. Suitable for production use after staged rollout.
Special Release (SR): A targeted build that quickly addresses a specific issue. Typically provided upon customer request.
Early Access (EA): Preview versions of upcoming software milestones. Intended for testing teams; not suitable for production environments.
Internal Release (IR): A build intended exclusively for the internal Exosys engineering team — development, debugging, and validation of experimental features or fixes. Not available to customers, testers, or the public.

Image tags¶

Each release version maps to three Docker image tags produced by the build pipeline:

Tag	Audience
`enforcegate/<component>:<ver>`	Production release (cosign-signed).
`enforcegate/<component>:<ver>-test`	Pre-release validation build.
`enforcegate/<component>:<ver>-dev`	Development build with relaxed verification.

Where <component> is one of standalone, engine, squid-connector, or captive-portal. The standalone image is the primary customer deliverable.