Record one deployment of a release in its deployment log (D198) — environment, artifact, commit, build URL, time, result, notes; append-only.
add_release_deploymentRecord one deployment of a release in its deployment log (D198) — environment, artifact, commit, build URL, time, result, notes; append-only.
Appends one entry to the release's deployments (D198 (3)): seq, by, agent and recorded_at are set by board-core; deployed_at defaults to now, result to deployed. Project admins and release managers, and an AI agent with its user's rights (MCP / PAT / OAuth, D144 agent account) — in any state, planned or released (a deploy or rollback after the release is shipped is recorded too). Recording is a record, not an approval: it never ticks the gate, locks the baseline, changes the scope or ships the release. No version: board-core retries on a concurrent write itself. Entries are never edited or removed — record a new one to correct. 409 deployment_log_full at 500 entries. Releases off → 403 feature_disabled; free plan → 403 plan_required; members and viewers → 403 forbidden.
Record one deployment of a release in its deployment log (D198) — when the user asks you to log a deploy, or right after you deployed it yourself: environment (an environment id such as production, or free text), artifact (what was deployed, e.g. an image tag), optional commit (lowercase hex SHA), build_url (http/https link to the build), deployed_at (default now), result (deployed default, verified, failed, rolled_back) and notes (Markdown: put the verification results here), plus a short reason. Works in any state, planned or released (a deploy or rollback after shipping is recorded too); needs your user to be a project admin or release manager (else 403 forbidden), releases on (403 feature_disabled) and a paid plan (403 plan_required). No version. The log is append-only: entries are never edited or removed — record a new one to correct a mistake; 409 deployment_log_full at 500 entries. Recording is a record, never an approval: it does not tick the gate, lock the baseline, change the scope or ship the release — those stay with people in the web app. Members see an entry's environment, artifact, commit, time and result, but not its notes or build_url.
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_key": "<project_key>",
"release_id": "<release_id>",
"environment": "<environment>",
"artifact": "<artifact>"
},
"name": "add_release_deployment"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| notes | No | Markdown, e.g. the verification results. | |
| commit | No | Commit SHA (7–64 lowercase hex). | |
| reason | No | Spec D144: why you make this change (≤ 200 characters). Optional, but give it when you act as an agent account — it is shown in the agent's run log ("moved KJ-12 To Do → In Progress because <reason>"). board-mcp records it in `agent.run`; board-core / board-files accept it and ignore it (it never changes the file, the version or the history). | |
| result | No | deployed | |
| artifact | Yes | What was deployed, e.g. an image tag or package name. | |
| build_url | No | ||
| release_id | Yes | Release id (spec D113): `R-` + a number, unique in its project; the file is `releases/R-{n}.md`. | |
| deployed_at | No | RFC 3339 timestamp with offset, e.g. `2026-09-23T09:00:00+07:00`. | |
| environment | Yes | An environment id of the project (e.g. production) or free text. | |
| project_key | Yes | Project key, e.g. `KJ`. 2–10 chars, uppercase letters and digits, starts with a letter. |