v0.2.2 Coming Tonight! · Circuit Breaker

⚡ v0.2.2 — Stability, Security & Smarter Foundations

Hey everyone,

It’s only been a few days since v0.2.0 dropped on Monday, but a lot has happened. v0.2.2 is landing today with meaningful improvements across stability, security, and UX responsiveness. Here’s what changed and why.

🔔 Notifications & Scan Progress — Now Actually Reactive

v0.2.0 shipped with notifications and scan progress indicators that were functional but sluggish. Updates weren’t pushing when they should have been, and scan feedback felt detached from what was actually happening in the background.

v0.2.2 tightens this up considerably. Notifications now fire in sync with real backend events, and scan progress reflects actual job state rather than polling on a delay. If something is happening, you’ll see it.

🔐 Security Overhaul (Pending Final Testing)

This is the big one. A focused security pass has been completed and the patches are staged in the SECURITY_PATCHES directory on the dev branch, pending final validation before merge to main.

Without getting ahead of the testing gate — the surface area covered includes auth hardening, input handling, and session integrity improvements. Details will be fully documented in the release notes once patches land on main. Watch the dev branch if you want an early look.

🔑 Password Reset — Simplified to Vault Token

After working through the email reset flow, the decision was made to streamline password recovery to vault token only for now. The email reset path introduced more moving parts than the feature warranted at this stage, and reliability was inconsistent across different SMTP configurations.

What this means for you:

Password reset is handled directly through the credential vault
It’s faster, more predictable, and has no external dependencies
Email-based reset isn’t gone — it’s been moved to the QOL backlog and will return in a more polished form down the road

🛠️ Under the Hood

Stability improvements to the telemetry ingestion pipeline
Reduced noise from polling errors on the map page
General hardening across the API layer

📦 Upgrade

docker pull ghcr.io/blkleg/circuitbreaker:v0.2.2
docker compose up --force-recreate

As always — feedback, issues, and edge cases welcome below. The security
patch details will get a dedicated post once testing clears.

— Shawnji