Release notes
Customer-facing notes for every tagged OrbitalReg release. Each entry follows the same six-section schema so a procurement reviewer or on-call operator can scan one document and answer the three usual questions: what changed?, what do I need to do?, and does any of it break me?.
OrbitalReg uses CalVer (YYYY.MAJOR.MINOR); see Versioning policy for the cadence rules and upgrade guarantees behind the version string.
Schema
Every release-notes file in this directory carries the same shape:
markdown
---
title: <YYYY.MAJOR.MINOR>
date: <YYYY-MM-DD>
---
# OrbitalReg <YYYY.MAJOR.MINOR>
## ✨ Highlights
Two-to-three sentence customer-facing summary of what changed and
why it matters.
## 🔒 Security
- Security-relevant changes (default flips, hardened headers,
vulnerability fixes, posture reductions).
## 🚀 New features
- Customer-visible additions.
## 🐛 Bug fixes
- Customer-visible fixes.
## ⚠️ Breaking changes
(Omit this section if the release has none. When present, every
bullet must call out the operator action needed.)
## 📦 Upgrade notes
(Operator-relevant changes: new migrations, env vars, config
defaults, deprecations.)Sections Highlights, Security, New features, and Bug fixes are required on every release. Breaking changes and Upgrade notes are optional and are omitted when empty.
Releases
| Version | Date | Highlights |
|---|---|---|
| 2026.1.2 | 2026-05-07 | Multi-arch image build fix |
| 2026.1.1 | 2026-05-07 | Update-check default-OFF, admin sidebar consolidation, orbital migrate CLI |