v0.7.0

Orion Belt v0.7.0

Plugins are now a real, live-configurable platform — not a build-time afterthought.

Previously, plugins existed as a dynamic .so-loading mechanism that was never wired into any shipped artifact (Docker image, packages, or the QEMU lab), and had no UI or API to manage. This release replaces that entirely.

Plugin platform

• Plugins compile directly into orion-belt-server — no .so files, no CGO, no per-arch/libc build matrix. The server binary is fully static again.
• Enable, disable, and reconfigure any plugin from the Plugins page in the web console — takes effect immediately, no restart.
• Config is schema-driven: real form fields per plugin, not raw JSON. Secret fields show a partial reveal (xoxb****9f2c) so you can tell what's set without exposing it, and saving no longer requires retyping every credential — untouched secrets are safely preserved server-side.
• Shipped plugins: audit-logger (enabled and working out of the box), slack-notifications, email-notifications, webhook-notifications, and the new chatops-access-request.

New: chatops-access-request

Get access-request approvals where you already work:

• Slack & Discord — native interactive Approve/Deny buttons, with full request-signature verification on the way back in.
• Microsoft Teams & Rocket.Chat — signed, time-limited magic links (no bot/app registration required to get started).

Security

• WebAuthn/FIDO2 is now enabled by default (Docker, QEMU lab, lab compose configs). Note: the RP ID must match the hostname you actually access the console through — this is a WebAuthn spec constraint, not configurable away.

Console

• Dark and light themes — a toggle on both the login page and the main app shell, defaulting to light.
• Nav icons are now inline SVGs (thin outline, no fills) instead of static PNGs, so they render correctly in both themes and pick up an active-state glow via CSS instead of separate color variants.

Build & release

• make build-server, the QEMU lab scripts, and the GoReleaser release pipeline all rebuild the embedded web console before producing a server binary — the shipped UI can never lag behind a stale, previously-committed snapshot again.

Upgrade notes

• server.yaml's plugin_dir setting is removed (plugins are no longer loaded from disk). A plugins: block in server.yaml still works as a one-time seed on first boot; after that, use the Plugins page or admin API — the database is the source of truth.

Full Changelog: v0.6.0...v0.7.0