Update an existing release. Supports optional file upload/replacement via multipart/form-data.
The request body must be sent as multipart/form-data with:
data field (required): JSON string containing the release configurationfile field (optional): Binary file to attach to the release (max 10 MB)File handling:
file fieldfile field and set keepExistingFile to truefile field and set keepExistingFile to falseFile uploads require the team to have the classloader feature enabled (paid subscription).
API key authentication for development endpoints.
You can create API keys in your team's settings on the Lukittu dashboard.
Include the API key in the Authorization header as: Bearer YOUR_API_KEY
Example:
Authorization: Bearer lukittu_api_key_abc123def456...Your team's UUID. You can find this value in your team's settings on the Lukittu dashboard. UUID v4 identifier
The unique identifier (UUID v4) of the release. UUID v4 identifier
JSON string containing the release configuration. Must be a valid JSON object with the following fields:
version (string, required): Release version (3-255 chars, no spaces)productId (string, required): UUID of the productstatus (string, required): One of PUBLISHED, DRAFT, DEPRECATED, ARCHIVEDsetAsLatest (boolean, required): Whether to set this as the latest releasekeepExistingFile (boolean, required): Whether to keep the existing file when no new file is uploadedbranchId (string|null, required): UUID of the branch or nullmetadata (array, required): Array of key-value metadata objects (max 20)licenseIds (array, required): Array of license UUIDs to restrict access (max 30)Optional file to attach to the release (max 10 MB). Must have a file extension. Replaces any existing file.