Release OpenShell

For the intended release version and branch, inspect the latest passing prerelease and changes since the previous stable release. Present the candidate to the maintainer. Once approved, dispatch Release from that branch:

gh workflow run release.yml --ref main

Without tag, Release detects the highest prerelease version reachable from the selected branch, then selects its highest-numbered passing candidate. It stops if that version has no qualified candidate or already has a stable tag. Supply -f tag=vX.Y.Z to select a version explicitly or retry a stable release.

Use the support branch instead of main for a previous minor version. That branch must contain the updated release workflows. Release selects the highest-numbered vX.Y.Z-pre.N reachable from that branch with a successful Pre-release run triggered by that tag or dispatched on the same branch, and matching passing release-tag-v1 qualification evidence. Missing or expired evidence blocks promotion. Inspect the selected candidate in the promotion job summary. The entire Pre-release run must succeed, including publication. If qualification passed but publication failed, rerun the failed jobs before promoting the candidate.

Release creates vX.Y.Z at that exact commit, then rebuilds and publishes all stable artifacts without rerunning qualification. Embedded versions change, so stable artifacts are not byte-identical to the qualified prerelease. An existing stable tag may be retried only if it already points to the selected commit. Stable images are saved as OCI archives during the build and pushed under the stable version tags during publication. Their SBOMs are verified before updating latest; the qualified prerelease's commit-SHA image tags remain unchanged.