Fix: Only update branch alias on major releases

[Copilot]

Branch alias was being bumped on every release (e.g. v2.2.6 → 2.3.x-dev), when it should only change on major releases and use the {MAJOR}.x-dev format.

Changes

• Guard clause: Skip alias update for any release where MINOR != 0 or PATCH != 0
• Alias format: Changed from ${MAJOR}.${NEXT_MINOR}.x-dev → ${MAJOR}.x-dev
• Validation: Extended numeric check to include PATCH (consolidated duplicate IFS read)
• README: Updated documentation to correctly describe the {MAJOR}.x-dev format and that only major releases (vX.0.0) trigger a branch-alias update

Behavior

Release	Before	After
v2.2.6	Updates alias to 2.3.x-dev	Skips — no update
v2.3.0	Updates alias to 2.4.x-dev	Skips — no update
v3.0.0	Updates alias to 3.1.x-dev	Updates alias to 3.x-dev

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Don't update branch alias for minor or patch releases</issue_title>
<issue_description>When releasing for example v2.2.6 of a package, the branch alias should stay at 2.x-dev, not be bumped to 2.3.x or something.

Only when releasing v3.0 should it then be changed to 3.x-dev</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Don't update branch alias for minor or patch releases #224

---

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.