release-pr workflow: auto-bump skips beta increment, always bumps patch

[thepagent]

Problem

When the release-pr.yml workflow runs with default bump=patch and no explicit version, it always strips the pre-release suffix and bumps the base version — even when the current version is already a beta.

Current behavior:

• Chart.yaml has 0.7.2-beta.1
• Workflow strips -beta.1 → gets 0.7.2
• Bumps patch → 0.7.3
• Result: 0.7.3-beta.1 ❌

Expected behavior:

• Chart.yaml has 0.7.2-beta.1
• Detect existing beta suffix → increment beta number
• Result: 0.7.2-beta.2 ✅

This means 0.7.2 can never get a second beta or a stable release through the default auto-bump flow.

Root cause

In .github/workflows/release-pr.yml, the resolve version step unconditionally strips the pre-release suffix and bumps:

CURRENT=$(grep "^version:" charts/openab/Chart.yaml | awk "{print \$2}")
BASE="${CURRENT%%-*}"
# ... always bumps patch/minor/major on BASE
VERSION="${major}.${minor}.${patch}-beta.1"

Suggested fix

If the current version already has a -beta.N suffix, increment N instead of bumping the base version:

if [[ "$CURRENT" == *-beta.* ]]; then
  BETA_NUM="${CURRENT##*-beta.}"
  VERSION="${BASE}-beta.$((BETA_NUM + 1))"
else
  IFS="." read -r major minor patch <<< "$BASE"
  case "${{ inputs.bump }}" in
    major) major=$((major + 1)); minor=0; patch=0 ;;
    minor) minor=$((minor + 1)); patch=0 ;;
    patch) patch=$((patch + 1)) ;;
  esac
  VERSION="${major}.${minor}.${patch}-beta.1"
fi

Impact

PR #271 was created as v0.7.3-beta.1 when it should have been v0.7.2-beta.2.