CI releases

Use a project CI token against the admin plane (default :8081):

Method	Path
GET, POST	/api/v1/admin/projects/{project_ref}/ci-tokens
DELETE	/api/v1/admin/projects/{project_ref}/ci-tokens/{token_id}
POST	/api/v1/admin/projects/{project_ref}/ci/releases

GitHub Actions (or any CI/CD platform): store the token as a secret, then POST ci/releases after the build. Job progress is not on this page: GET /api/v1/admin/jobs/{job_id} (admin reference).

Not how KiriVers itself is released

A CI token here belongs to your project's pipeline, uploading release packages to KiriVers. The build and release pipeline for KiriVers itself is documented in Contribute → Release and Docker.

Explorer: API reference (openapi.admin.json; open Scalar).