fix: check major and minor versions are tracking [ED-24551]

[davseve]

✨ PR Description

1. Problem & Context

Beta version validation wasn't checking that major/minor versions increment correctly between release lines. ED-24551 requires stricter tracking — beta releases can only increment patch on same line, or bump to next minor/major with beta1.

2. What Changed (Where)

• current-version-validation.ts: Refactored validateNextBeta() to enforce next-minor (x.y+1.0-beta1) or next-major (x+1.0.0-beta1) transitions, replacing generic "must be beta1" check.
• current-version-validation.test.ts: Expanded test cases to cover valid transitions and rejection of invalid version jumps (4.4.0, 5.1.0, 6.0.0, etc.).

3. How It Works

Same-line beta increments require exact latestBetaNum + 1 sequence. New-line transitions must be precisely nextMinor or nextMajor (both with -beta1); any other version string fails with clear expectation message.

4. Risks

Low — validation tightens constraints (should reject more invalid states, not break valid ones). Test coverage is comprehensive for edge cases.

Generated by LinearB AI and added by gitStream.
_{AI-generated content may contain inaccuracies. Please verify before using.
💡 Tip: You can customize your AI Description using Guidelines Learn how}