Release: seal a software release
release_sealSeal a software release: its file fingerprints, source commit and SBOM fingerprint, anchored on chain. Customers check any download with release_check. A sealed release cannot be changed. Requires the organization API key.
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": {
"product": "<product>",
"version": "<version>",
"files": "<files>",
"actor": "<actor>"
},
"name": "release_seal"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| actor | Yes | Who is doing this (person or agent) | |
| files | Yes | Release files, each {"name": "app-1.4.2.zip", "sha256": "<64 hex>"} | |
| commit | No | Source commit the release was built from | |
| product | Yes | ||
| version | Yes | e.g. 1.4.2 | |
| sbom_sha256 | No | Fingerprint of the software bill of materials, if you have one |