`codes.release.manage`

Generated at 2026-09-23 23:26:36 UTC from openvibe-contracts v0.33.0 and openvibe-sdk v0.5.0.

Grantable to apps: request it for an app on its project page. Network approves it only inside the project's allowance.

An app manages release metadata for ITSELF with its own token (audience openvibe.codes): create a release from a validated app or mod manifest, publish, deprecate (with a reason and an optional replacement) and revoke it. The token's sub must be app:<the app in the path>; people manage releases in the portal with their project role instead. Trust tiers are not part of this capability (staff metadata only).

Owner

codes (token audience openvibe.codes)

Version

1.0

Status

active

Visibility

public

Resource constraints

owner, project

Quota class

codes-release-write

Permissions

codes:releases:write

Input

codes.app-manifest@1

Events

codes.app.published, codes.app.deprecated, codes.app.revoked

Implemented by

POST /api/v1/apps/:app/releases
POST /api/v1/releases/:id/publish
POST /api/v1/releases/:id/deprecate
POST /api/v1/releases/:id/revoke