release-orchestrator

End-to-end release orchestration automates the full workflow from unreleased code version bumps through creation and verification. It enforces changelog checks before tagging and applies guardrails around 0.x.y prerelease versions to ensure deterministic, validated releases.

Yes, you can resume the complete release workflow end to end. The orchestrator handles the lifecycle from initial version bump to post-release code bump, allowing you to run or resume the process while maintaining versioning discipline and safety checks.

Guardrails for 0.x.y prerelease versions enforce deterministic commands and validation steps. They ensure a CHANGELOG entry exists before release tagging and validate each release step to prevent inconsistent prerelease lifecycle updates.

A changelog entry is required before tagging to enforce release safety and traceability. The orchestrator checks for CHANGELOG presence as a validation step, ensuring no release is tagged without documented changes for the target 0.x.y version.

Yes, post-release version bumps are handled automatically. After creating and verifying the release, the orchestrator updates published versions and applies the next code-version bump to prepare the repository for future development.

Use an automated release orchestrator to manage prerelease lifecycle scenarios. It eliminates manual version checks by applying deterministic commands and guardrails around 0.x.y series, orchestrating tagging, changelog updates, and subsequent bumps.