Expand description
Release page management — torii release ….
Both GitLab and GitHub expose “Release” entities: a named tag-anchored object with a description (markdown) and a list of assets (links and/or uploaded files). gitorii’s CI creates these via the API; this module is the CLI surface to edit notes, fix typos, and delete bad releases without having to rebuild the entire pipeline.
Asymmetries between platforms (documented inline where they exist):
- GitLab: release description is one Markdown blob plus a list of
asset links (URLs pointing into the Package Registry). To
“delete an asset” you delete the package (
torii package delete), the release re-renders the link list automatically. - GitHub: release description is one Markdown blob plus uploaded binary assets attached directly to the release. Each asset has its own id and is deletable.