Repository navigation
Versions
This page explains the current alpha-stage version scheme, the active version,
and where historical release records live. VERSION.json is the version
authority.
| Field | Value |
|---|---|
| Version | vA3.11.0 |
| Current version | A3.11.0 |
| Current tag | vA3.11.0 |
| Released | 2026-07-03 |
| Channel | Internal alpha |
| Previous expression for the same tree | 0.11.0-alpha.3 |
| Release policy | No GitHub Releases during alpha. |
A3.11.0 re-expresses the same source tree that was previously described as
0.11.0-alpha.3. The change is a versioning and release-policy alignment, not
a runtime feature change by itself.
While MCOS is in alpha, versions use:
A{alphaIteration}.{feature}.{patch}
For A3.11.0:
| Segment | Meaning |
|---|---|
A |
Alpha-stage channel. |
3 |
Third alpha iteration. |
11 |
Feature line. |
0 |
Patch/hotfix number. |
installer/Build-Msi.ps1 maps this to a four-part Windows Installer
ProductVersion. A3.11.0 maps to 3.11.0.0.
-
VERSION.jsonownscurrent_version,current_tag,released_at, andlast_release_commit. -
CHANGELOG.mdrecords human-readable release history and[Unreleased]documentation or maintenance changes. - GitHub Releases are deferred until MCOS leaves alpha.
- The Windows Build, Test, and Package workflow is the per-commit health gate.
- Historical semver-alpha entries remain historical and should not be presented as the current release.
| Version | Date | Historical theme |
|---|---|---|
A3.11.0 |
2026-07-03 | Alpha-stage scheme migration for the 0.11.0-alpha.3 tree. |
0.11.0-alpha.3 |
2026-07-02 | PHASE-14 diagnostics slices B-E, security hardening, and 2026-06 bug-campaign fixes. |
0.11.0-alpha.2 |
2026-05-15 | Optional gateway TLS dual-bind. |
0.11.0-alpha.1 |
2026-05-15 | First internal alpha package for the v0.11.0 line. |
0.11.0 |
2026-05-15 | Diagnostics Slice A route surface. |
0.9.x through 0.10.x
|
2026-05 | Gateway, discovery, worker-pool, telemetry, and packaging iterations. |
0.7.0 |
2026-05-05 | Gateway-first architecture milestone. |
0.6.x |
2026-05 | Realignment phase delivery and native gateway maturation. |
0.5.0 |
2026-04-25 | LAN client control-plane model. |
For full entries, read VERSION.json, CHANGELOG.md, and retained reports
under docs/archive/realignment-release-reports/.
Documentation-only changes should normally stay under [Unreleased]:
## [Unreleased]
Do not change VERSION.json.current_version unless the maintainer directs a
version cut. When a version cut is directed:
- Update
VERSION.json. - Move relevant
[Unreleased]changelog content under the new version heading. - Run existing metadata checks.
- Build, test, and package through the Windows product gate.
- Tag only when the version is intentionally cut.
It names the same tree in the current alpha-stage scheme. Treat
vA3.11.0 as the current version string.
They are valid in historical release notes, archive reports, and changelog history. They should not appear as the current release in README, Home, Release Gate, or live wiki front-door pages.
installer/Build-Msi.ps1, function ConvertTo-MsiProductVersion.
Release Gate | Packaging and Gateway Binary | Operations | Home
Source for this wiki is maintained under docs/wiki/ in the Master-Control-Orchestration-Server repository.
Setup
Connect Clients
Operate
- Daily Operations
- Dashboard
- Telemetry and Activity
- Gateway
- Worker Pools
- Sub-Agents
- Governance
- CLU Governance
- Privileges
Maintain
Troubleshoot
Reference