Release notes
Customer-facing release notes for the AlphaSwarm. New
entries land here whenever a PR's Changeset is marked
audience: customer or audience: both (see
.changeset/README.md).
Published posts render at /blog — latest: July–August 2026 — Safety gates, latency visibility, and BYOK. This folder holds the process description and the archived long-form entries.
For the full technical changelog (every commit, including non-customer-facing internal refactors), see CHANGELOG.md.
Current shipped version
| Field | Value | Source |
|---|---|---|
| Deployment version | 0.1.0-alpha.1 | AGENTS hard rule 65; alphaswarm_platform/configs/deployment/topology.yaml app_version; Kubernetes app.kubernetes.io/version and alphaswarm.io/deployment-version |
| Operator CLI | 0.1.0-alpha.1 | alphaswarm_cli __version__ / alphaswarm-cli --version |
| Monolith package | 0.1.0 | alphaswarm/pyproject.toml |
| Docs site package | 0.1.0 | alphaswarm_docs/package.json and this repo's CHANGELOG.md [0.1.0] (2026-06-18) |
Git tag v0.1.0-alpha.1 | not published on the runtime repos as of 2026-08-15 | git tag -l 'v*' on alphaswarm |
Sibling packages may carry their own SemVer (for example
alphaswarm_core is independently versioned). Those numbers are not
the platform deployment version. Operators should pin images and
cluster labels to 0.1.0-alpha.1.
Subscribe
- RSS / Atom feed: built from this folder by Docusaurus — available at /blog/rss.xml.
- In-product changelog widget: powered by
/release-notes.json(Headway-compatible). - Email digest: opt in from the operator UI profile menu.
API epochs
AlphaSwarm uses Stripe-style date-epoch API versioning. New epochs:
- Roll out on the first of the month (
2026-06-01,2026-09-01, …). - Preserve old contracts via the
Deprecation/SunsetHTTP headers (RFC 8594) for a 12-month sunset cycle. - Move to archive.alpha-swarm.ai when fully retired.
The matching reference docs live at /reference/api/.