Promote a version to a deployment target
Once a version is complete, promote it to one of the deployment targets you configured in project settings.
In the appVersion detail
Once a version is complete, promote it to one of the deployment targets you configured in project settings.
Maleus doesn't host your code itself. It tracks which version is running where. To promote a version you first define one or more deployment targets in project settings (each one is a name plus a git branch), then promote completed versions to them from the versions list.
Set up your deployment targets
Deployment targets live in Settings → Deployments. A target is just a label and a branch in your connected git remote. Name them however you like (
staging,prod,canary…).Only admins can create or edit deployment targets.
Promote a version
Versions become promotable once they're marked Done. They move to the Ready to Deploy column on the versions list.
The actual rollout (CI, hosting provider) is whatever your repo and infrastructure do when that branch receives commits.
Watch your deployments
The Deployments page in the project sidebar gives you a unified view of every environment your project ships to: live status, identity (commit / version), logs, and SRE-agent shortcuts.
What runs where, how it behaves, and what changed.
Keep one target per stage (e.g.
stagingandproduction) and always promote staging first. The versions list lets you promote independently to each target, so you can validate on staging without blocking other work.Empty state
If you don't see any deployment column yet, you haven't added a target. The Deployments card shows No deployment targets. Add deployment targets in Settings to promote versions. with a shortcut button to settings.