release-stable

To automate a stable production release, the workflow intelligently detects whether to finalize an existing beta or perform a direct stable release based on your current version and CI/CD context. It then handles automated tagging and publication.

Release notes are generated automatically through commit analysis during the release workflow. The system applies quality validation to ensure correct formatting, including bilingual EN/FR release notes with a clear approval path.

Strict versioning rules are enforced natively by the release workflow during the automated tagging process. The system validates the version context before finalizing a beta or publishing a direct stable release.

Yes, the release automation operates entirely through its internal scripts component without requiring any external dependencies. It runs directly on your main branch to analyze commits and manage the publication pipeline.

Yes, the stable release workflow includes automated quality validation specifically for bilingual EN/FR formatting. It generates and formats the release notes automatically while enforcing these language controls.

Automated beta finalization promotes an existing pre-release version to stable, while a direct stable release bypasses the beta phase entirely. The workflow intelligently detects the correct approach based on your current version and workflow context.