[Copilot]

When the intended release version already exists, the workflow should publish an improved release without changing the base version. This change switches collision handling from patch auto-increment to revision suffixing (+rev1, +rev2, ...).

• Release tag collision behavior

  • Keep the original computed tag if it does not exist.
  • If it exists, derive the next available revision tag on the same base version.
  • Example progression: v01.02.03 → v01.02.03+rev1 → v01.02.03+rev2.

• Tag selection logic update

  • Replaced the previous “increment semantic/hex patch until free” loop in find_available_tag.
  • Added logic to scan existing base+rev* tags, extract numeric revisions, and select max+1.

• Compatibility with existing flow

  • Preserves downstream steps (verify_tag, tag creation, release notes/release publishing) by only changing the selected available_tag format.

# Before (collision)
v01.02.03 -> v01.02.04

# After (collision)
v01.02.03 -> v01.02.03+rev1

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None