12 added, 0 removed. Audit A to A.
---
name: release
description: Publish a Unica version to the public marketplace, or resume a release that stalled part-way. Use when asked to cut, ship, promote, or finish a release, or when consumers still see an older version than the latest tag.
argument-hint: [version, for example v0.9.2]
---
# Release Unica
Follow [docs/release-runbook.md](../../../docs/release-runbook.md). It is the
authoritative procedure; do not improvise an order.
+ ## Most of it is automated
+
+ Release Warden merges the staging pull request, requests the promotion, and
+ merges the promotion, each once its checks are green. The user's part is two
+ tags: the source release tag and the marketplace tag. Before doing any of those
+ steps by hand, check whether the warden is simply about to do it:
+
+ ```bash
+ gh workflow run release-warden.yml --repo IngvarConsulting/unica -f dry_run=true
+ gh run list --workflow "Release Warden" --repo IngvarConsulting/unica --limit 3
+ ```
+
## Before anything
Establish where the release already is, because most requests are to *resume*
one rather than start one. Check in this order and enter the runbook at the
first unfinished step:
```bash
gh release list --repo IngvarConsulting/unica --limit 3
gh api repos/IngvarConsulting/unica-marketplace/tags --jq '.[0].name'
gh pr list --repo IngvarConsulting/unica-marketplace --state open
gh api repos/IngvarConsulting/unica-marketplace/contents/.agents/plugins/marketplace.json \
--jq '.content' | base64 -d | grep '"ref"'
```
A source release whose tag is newer than the catalog `ref` means the release is
live for nobody. That is the common stall, and it is silent.
## When something goes wrong
Only the promotion merge is visible to consumers, so before it aborting just
means closing a pull request. After step 1 a version is burnt: never re-cut it
with different bytes, take the next patch instead. Rolling back a live release is
a revert of the promotion commit, which is safe because published bytes never
move. See the runbook's abort and rollback tables.
## Rules
- Never move or delete a published tag, and never force-push the marketplace
default branch. A catalog naming a missing tag breaks every install, and it is
the only genuinely corrupt state this process can reach.
- Tag the staging merge commit, not the promotion commit. The promotion pull
request cannot go green before that tag exists.
- Stop and ask before merging anything in `unica-marketplace` or creating a tag.
Those are the publishing steps and they are the user's call.
- Signing is the user's: the key is theirs and the passphrase must not be handled
for them. If `gpg` fails with `Operation cancelled`, tell them to unlock it and
give them the exact tag command to run.
- Report each step's verification output rather than asserting success.