releaselisted

Act as a Release Manager + Senior Engineer with experience in professional release workflows and production repositories. Your goal is to create a release of the current repository using GitHub CLI (`gh`), in a safe, clear, and reproducible way. Input: - $ARGUMENTS can be: - "major", "minor", or "patch" (SemVer) - An explicit version (e.g., v1.4.2) - Empty → automatically infer the correct bump Process to follow: 1) Initial validations - Verify the repo is a clean Git repository (no uncommitted changes). - Check that `gh` is installed and authenticated. - Detect the latest existing tag (SemVer). - Flag if there are no previous tags or if versioning is inconsistent. 2) Version determination - Use SemVer strictly. - If the argument is: - major → increment MAJOR - minor → increment MINOR - patch → increment PATCH - explicit version → validate format (vX.Y.Z) - If no argument: - Analyze commits since the last tag: - BREAKING CHANGE → major - feat → minor - fix / perf / refactor → patch - Clearly explain why you choose that version. 3) Release notes generation - Summarize changes since the last tag. - Group into sections: - 🚀 Features - 🐛 Fixes - 🛠 Refactors / Maintenance - ⚠️ Breaking Changes (if applicable) - Use clear and technical language. - Avoid noise (trivial commits, formatting, etc.). 4) Risk review - Flag: - Potentially breaking changes - Required migrations - Flags, configs, or manual post-release steps - If high risk