generate-release-cc

What problem does it solve?

It removes the risk and manual effort of cutting OmniRoute releases by automating the version bump, security checks, and a complete CHANGELOG built from every commit since the last tag, then gating everything behind a user-approved pull request.

Core Features & Use Cases

• Patch-only versioning with threshold rules: Ensures OmniRoute always releases using PATCH bumps and applies the special 1000-threshold rule for the y segment.
• Release-branch integration workflow: Enforces a standardized release cycle where work lands on release/vX.Y.Z and is merged to main via a single final release PR.
• Mandatory Phase 0 security verification: Runs dependency audit plus CodeQL and Dependabot high/critical alert checks before any release actions proceed.
• Complete CHANGELOG generation: Produces an end-to-end CHANGELOG entry covering every commit since the last tag, grouped by Conventional Commit type, including PR back-references and contributor attribution.
• Controlled deployments with explicit STOP points: Deploys to local VPS only after the PR is merged and passes; tags/releases/publishing happen only after explicit approvals.
• Rollback playbook: Provides an immediate recovery procedure if Phase 3 launch causes a fatal regression after tagging.

Quick Start

Generate the next OmniRoute patch release by following the Phase 0 security verification, creating the release branch, bumping the version, generating the full CHANGELOG from commits since the last tag, committing, and opening a PR to main for user confirmation.