release

Git release orchestration is automated by enforcing green pre-flight gates, explicit user authorization, and correct tagging workflows before publishing. This ensures merge states are validated and artifacts are published only after approval.

A pre-flight gate in CI release workflows is a validation check that must pass green before tagging or publishing begins. It validates version pins, merge states, and explicit user lock signals to ensure release readiness.

Explicit user authorization is enforced through lock signals that must be satisfied before triggering release steps. The workflow requires these signals alongside green pre-flight checks before executing any tagging or publishing actions.

Yes, release orchestration covers both cut releases and tag pushes alongside publishing across GitHub and crates.io. It applies pre-flight gates, tag authorization, post-tag verification, and rollback readiness to the entire workflow.

Post-tag verification automatically validates the release state after tagging, ensuring rollback readiness and incident escalation rules are in place. It also confirms audit-friendly release notes and scratchpad updates are completed.

Automated release orchestration should not proceed when pre-flight checks are not green or explicit user lock signals are absent. Counter-pattern safety rules halt the workflow if validation, version pin checks, or authorization requirements are unmet.