Hey Anna app developers! 
A short but mighty stretch this time — four releases packed with things you’ve been asking for: becoming a developer is now one click away, Cloud Agents got twice the muscle, and the publish → review → release pipeline lost its sharpest edges. Let’s dive in! 
New Features
-
Self-serve developer activation (beta.124) — No more waiting for manual approval! Any user with a verified email can now become a certified developer in one click: hit the new POST /developer/profile/activateendpoint (or just follow the activation card in the developer console), accept the developer ToS, and you’re in. Idempotent, instant, and the navbar entry lights up right away. Building for Anna has never had a lower barrier — invite your friends!
-
Cloud Agents upgraded: 2 CPU / 2 GB → 4 CPU / 4 GB (beta.125, forum #214) — Browser-rendering workloads (PPTX export, Puppeteer/Chrome-heavy Executas) were measured pushing right up against the old 2C/2G ceiling — causing export timeouts and brief machine stalls. All Cloud Agents now run on 4 cores / 4 GB, with /dev/shmdoubled to ~2 GiB. Best part: second-level wake-up and idle-suspend cost savings are fully preserved (resume still clocks in at ~1.5s
). Existing machines converge automatically via rolling upgrade — no action needed on your side. -
Agent system metrics, visualized (beta.123) — The Agents page now shows live CPU / memory / disk usage bars for both local and cloud agents (color-coded at 70% / 90% thresholds, with used/total detail). Metrics soft-refresh every 30s in sync with heartbeats — no skeleton-screen flicker, and polling pauses when the tab is hidden. Great for spotting a resource-hungry Executa at a glance! 
-
Real-time install progress in the App Store (beta.123) — Your app’s Install button now shows live “Installing… N%” progress, streamed over SSE with a polling fallback. Progress survives page refreshes (state is derived server-side), the install console re-attaches when users reopen the detail drawer mid-deploy, and failed deploys roll the button cleanly back to Install. Your users get a much more confident install experience — for free. -
Publishing guardrails (beta.124) — With self-serve activation open, we added sensible anti-abuse limits: app creation (default 10/day), review submissions (default 5/day), and active apps per developer (default 20 — dev sandbox placeholders don’t count). Normal workflows won’t ever notice these; they just keep the store healthy for everyone. 
Bug Fixes
-
“Approve” no longer explodes with VersionConflictError (beta.126) — If your Executa content drifted after a version was cut (e.g. re-pushing a binary under the same version), the admin clicking “Approve” used to get a 400 and your release stalled. publish_versionnow reuses the frozen snapshot from cut time instead of re-resolving live Executa rows — what you cut is what ships.
-
Fail-fast release precheck at submission (beta.126) — Version conflicts and other release-blocking issues are now caught the moment you submit for review: a dry-run of the real freeze logic (zero writes, fully rolled back) returns a clear 400 “release precheck failed” straight to you, instead of silently piling up in the admin review queue. Fix it in seconds, resubmit, done.
-
Release candidate selection unified (beta.126) — Fixed a latent bug where approve-with-publish could accidentally pick a 0.0.0-draftprojection row as the release version. Submission precheck and admin approval now share onepick_release_candidate— always the newest real version. -
Install console no longer flickers (beta.123) — High-frequency progress events now patch the progress bar in place instead of rebuilding the whole panel (which restarted CSS animations and made the drawer flash). Structural events are batched per animation frame, and log lines never trigger a full re-render. Buttery smooth. 
Compatibility Notes
Everything is additive — no manifest changes, no SDK bumps required. Existing apps keep working unchanged.
One badge semantic change: with developer activation now self-serve, the “Verified developer” store badge is reserved for first-party (Official) apps only. Your app listing itself is unaffected.- If your Executa was hitting memory/CPU walls on Cloud Agents (Chrome, exports, heavy rendering) — just try it again. It probably works now.
Feedback Welcome!
Just activated your developer profile? Got a Chrome-heavy Executa finally rendering in peace on 4C/4G? Hit a rough edge in the new release precheck? Drop your questions, feedback, or showcase posts below — we read everything. Happy building!