How are MonkeyCode upgrades and updates handled?
For self-hosted deployments, upgrades and rollback are operational decisions you own: stage new releases, back up first, and verify task state after upgrading.
Important context
Confirm the release and versioning process, and test one staged upgrade and restore before inviting a wider team.
| Ownership (self-hosted) | Operator manages upgrades and rollback |
|---|---|
| Before upgrading | Back up and stage the release |
| After upgrading | Verify task state |
| Verify | Release and versioning process |
What to do next
Prove one staged upgrade and a restore in a non-production environment before inviting a wider team.