Atelier v0.23.0-beta

Last release introduced outbound event webhooks, but you could only script against them through the admin API, and only alert-sourced events fired. This release finishes the job: the whole build lifecycle now emits events, and a Settings panel manages subscriptions with no API calls. Alongside that, your deployments now tell the truth about exactly which commit is live, builds stop quietly rewriting your repo, and the agent building an app can read its own post-build review.

Coming from v0.22.x? Straight upgrade — one command, nothing you already run changes. Still a beta: the now-complete event-webhook system is the headline and is getting a soak before the next stable tag.

Event webhooks, finished

Last release promised that a Settings panel and the full set of build lifecycle events would follow. They’re here.

The build lifecycle now emits events. Every build sends build.started, then exactly one terminal event:

build.succeeded — built and live; carries the source commit and the build id, so a receiver can fetch the build record.
build.failed — a hard build or deploy failure.
build.held — the pre-deploy lint gate held the deploy under the Hardened profile. This is not a failure: the previous version keeps running and an operator can override it, so your monitor should treat it differently.

And there’s now a Settings → Automation → Event webhooks panel (admin only): register a receiver URL and shared secret, subscribe to everything or pick exact event types, enable or disable without deleting, send a test event, and see each subscription’s last delivery result at a glance. No more curling the admin API to wire up a monitor — though the API is still there if you prefer it.

Deployments that tell the truth

App detail now reports the exact commit that’s actually running — the source SHA you pushed, the build that produced it, and whether it’s live — not an inferred guess. An agent (or you) can confirm a deploy landed the code you intended instead of assuming.

The bigger change is what builds stopped doing: a build no longer commits its generated files — the build spec, the Kubernetes manifests — back to your repository. Your Git history stays yours, the reported version is honest about what’s deployed, and a push-to-build loop no longer has to git pull --rebase to reconcile a commit the platform made behind your back. Bring-your-own-code just got quieter and more predictable.

The build agent reads its own review

When the optional post-build code review runs, its findings now reach the agent that built the app — a pointer in the build log plus skill guidance on where to read it — so the agent can act on the review instead of it landing only in the UI for a human to notice.

A table view for your apps

The Apps page can now switch between the card grid and a compact table — easier to scan when you’re running a lot of apps. This also fixes a dropdown that flickered when it overlapped a neighbouring card, which could make Archive impossible to click. The unused Token Usage view was retired in the same pass.

Two legacy tools retired

The standalone atelier-mcp server and the atelier-compose exporter are gone. The portable Agent Skills (atelier-build, atelier-operate) are the canonical way for any agent to drive the platform now; both of these predated the skills and had become more confusing than useful. Hosting your own MCP servers as apps is unaffected — this is only the removal of the old platform-control MCP shim and the compose-file export.

Skills

atelier-build and atelier-operate gained guidance on reading the new deployment provenance (confirm what’s live from the running source commit) and on picking up post-build review feedback from the build log.

Upgrade

For everyone — one command:

curl -Lo upgrade.sh https://tryatelier.blob.core.windows.net/tryatelier/latest/upgrade.sh
chmod +x upgrade.sh
./upgrade.sh v0.23.0-beta

It rolls atelier-core, atelier-ui, and the MCP server pods. Your running app pods aren’t touched; folders, pins, alert channels, event-webhook subscriptions, public-access configuration, and MCP server deployments carry over unchanged.

Bug reports and feedback in the testers Discord channel. Thanks for testing.