plugin-launcher-release-flow

To enforce strict commit message formatting for git release tags, use a workflow that validates the chore(release): vMAJOR.MINOR.PATCH format before tag creation. This prevents accidental mis-taggings and ensures CI triggers only fire on correctly structured releases.

The best way to synchronize local and remote git tags is to validate them during the release workflow before pushing. This ensures local and remote tags match, preventing conflicts that can break CI pipelines and disrupt release automation.

To trigger CI workflows automatically when pushing a new release tag, apply the correct chore(release): vMAJOR.MINOR.PATCH format and push the tag to origin. The enforced release flow validates the tag and initiates the CI workflows.

Yes, you can use pre-release tagging on feature branches without triggering the full release CI workflow. The release flow applies guardrails to distinguish between pre-release tags on feature branches and final tags on the main branch.

Your CI pipeline fails on incorrect version formats because the release workflow enforces strict chore(release): vMAJOR.MINOR.PATCH commit message rules. This validation prevents accidental mis-taggings from corrupting the release history.

Yes, automating plugin releases requires a git workflow that enforces correct release tagging, commit message rules, and CI triggers. This ensures releases involving main branches, feature branches, and pre-release tagging remain predictable and auditable.