elastic / cloudbeat / 28811847466
76%

DEFAULT BRANCH: main
Ran
Jobs 1
Files 245
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 76.1% (+0.007%) from 76.093%
28811847466

push

github

web-flow 
fix: bump main to next minor after minor branch-out (#7186)

## Summary

Prep for the Jul 07 minor FF
([context](https://elastic.slack.com/archives/C0JFN9HJL/p1780580577798249)):
release-eng will trigger our pipeline with `WORKFLOW=minor BRANCH=9.5
NEW_VERSION=9.5.0` — `NEW_VERSION` is the version for the **new
branch**, not for `main`, so each team owns bumping `main` to the next
minor themselves.

`main` is already on `9.5.0`. Today's `post-minor-merge.sh` only
branches out `9.5` and syncs `hermit.hcl` — nothing advances `main`
afterward, so it would stay on `9.5.0` indefinitely. (Confirmed this
isn't hypothetical: two ad-hoc "Bump to 9.6.0" PRs from the previous
cycle, #5608/#5609, were closed unmerged.)

- Add `next_minor_version()` semver helper to `common.sh`
- Add `bump_main_to_next_minor` step to `post-minor-merge.sh`, run
**after** branch-out (so `9.5` is cut while `main` is still `9.5.0`) and
before the hermit sync — opens a `Bump cloudbeat version to 9.6.0` PR,
same convention as prior manual bumps
- Reuses the existing `pr_exists` helper (matching `common.sh`'s
documented `BUMP_BRANCH` contract) instead of duplicating the open-PR
check
- Add matching PR body template

Replaces #7181, rebased on latest `main` (picks up the now-merged #7184
idempotency fix). Recreated on a fresh branch because pushing further
commits to the old branch was rejected with `GH006: 4 of 4 required
status checks are expected` — this has now happened on **two different
branches** after their PRs accumulated completed CI checks (both plain
pushes and force-pushes after rebase), while brand-new branches push
fine every time. This looks like a real, systemic policy issue worth
raising with release-eng/repo admins, since it'll recur on any PR that
needs a follow-up push.

## Test plan

- [x] Dry-run verified end-to-end against a scratch clone with
`WORKFLOW=minor BRANCH=9.5 NEW_VERSION=9.5.0 DRY_RUN=true` — correct
sequencing, semver math (`9.5.0` → `9.6.0`), commit me... (continued)

10202 of 13406 relevant lines covered (76.1%)

15.9 hits per line

Jobs
ID Job ID Ran Files Coverage
1 28811847466.1 245
76.1
 GitHub Action Run
Source Files on build 28811847466