Activate a release
activate_releaseSwitches an authorized project’s active route to a completely published retained release with revision checks. Returns the previous release as the rollback target.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"project_id": "<project_id>",
"release_id": "<release_id>",
"idempotency_key": "<idempotency_key>"
},
"name": "activate_release"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| project_id | Yes | Exact stable project ID. Resolve it first. Never invent an update target. | |
| release_id | Yes | ||
| idempotency_key | Yes | Unique write key. Reuse the same key and input after an uncertain response. | |
| expected_revision | No | Original base_revision in local .deploymonster.json; never substitute current server revision before reconciliation. | |
| overwrite_revision | No | Exact remote revision the USER explicitly agreed to overwrite after seeing change summary. | |
| overwrite_confirmation | No | Only after explicit user overwrite choice; never auto-confirm. |