PUBLIC BETA
Worlds beta releases
Notice version 2026-09-28
Release status follows the verified package record. Preparing a candidate or merging code does not publish a package.
Public beta 0.9.0-beta.2
This version's published package has been verified for website activation.
The beta scope is the local dashboard and CLI, current Stripe and native Zendesk subsets, supported combined workflows, saved tests and reviewed reports. Zendesk live API qualification remains pending. Read the current limitations before relying on a workflow.
Changes in 0.9.0-beta.2
Save confirmation waits for recovery state to be persisted. Reloading after a confirmed dashboard save retains the saved revision so the next save does not conflict with stale recovery state.
Native Zendesk user updates accept name only. Any supplied email, including an unchanged address, is refused before mutation; a simultaneous name change is not saved. Email remains supported when creating an end user. Agents that previously sent email in an update must omit that field. This is an explicit local limitation, not a reproduction of Zendesk identity management.
No additional connector operations or starter commands are included in this patch. Native Zendesk live qualification remains pending. Keep the safe JSON beside standalone native HTML reports for world-level failure details, and review the current limitations before updating.
Updating and recovering
Installation guides name a specific version. Your installed package does not update itself. Review each release's compatibility notes, stop the previous dashboard host and back up your project before changing versions. Reopen the same project only with a compatible version.
If an update fails, keep the original backup and contact arya@usesparta.co before changing saved data. Reinstalling an older executable does not reverse database or file changes. Disposable worlds may need to be recreated from their saved inputs.
What changes during beta
We will publish notes for released fixes, connector changes and breaking behavior here. Ongoing development is not a commitment to a particular feature or release date. Share your workflow through signup or support to help prioritize the next update.