[hedinasr]

PREQ-8673: Increase the v1→v2 migration seed buffer so new claims skip numbers already published to Artifactory.

Why

When no refs/build-number/* exist yet, v2 seeds MAX_CLAIMED from the legacy GitHub build_number property plus a buffer. The buffer was 1000. Repos such as sonarcloud-webapp kept publishing with v1 after that snapshot, so v2 later re-issued numbers Artifactory already had. multiRepoPromote then 500s (Multiple builds found for sonarcloud-webapp#N).

Change

• Seed with legacy + 10000 instead of legacy + 1000.
• Update the shellspec that asserted 42 + 1000 + 1 = 1043 to 10043.

This only affects the first claim in a repo that still has no refs/build-number/*. Repos that already have those refs are unchanged.

Test plan

• shellspec spec/get_build_number_spec.sh --shell bash — 18 examples, 0 failures

[hashicorp-vault-sonar-prod]

PREQ-8673

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues
0 New dependency risks

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[gitar-bot]

Code Review ✅ Approved

🟡 Medium risk

Increases the legacy build-number migration buffer from 1000 to 10000 to prevent v2 from re-issuing numbers already published to Artifactory when repos continue publishing with v1 after the initial snapshot. Shellspec test updated accordingly. No issues found.

Verification

Functional validation No results

Rules No rules evaluated

Auto-approval Not enabled

Set up

Options

Auto-apply is off → Gitar will not commit updates to this branch.
Display: compact → Counting what did not apply, without listing it.

Comment with these commands to change the behavior for this request:

Auto-apply	Compact
gitar auto-apply:on	gitar display:verbose

_{Was this helpful? React with 👍 / 👎 | Gitar}