• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

elastic / cloudbeat / 28796306233
76%
main: 76%

Build:
Build:
LAST BUILD BRANCH: dg-add-feat-flags
DEFAULT BRANCH: main
Ran 06 Jul 2026 02:03PM UTC
Jobs 1
Files 235
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

06 Jul 2026 01:46PM UTC coverage: 75.802%. Remained the same
28796306233

push

github

web-flow
fix: make version bump scripts idempotent on retrigger (#7184)

## Summary

Raised by Julien in
[#mission-control](https://elastic.slack.com/archives/C0JFN9HJL/p1783094800245129):
retriggering the centralized version bump pipeline for an
already-completed bump (9.4.4 / 9.3.8 / 8.19.19) failed instead of
succeeding as a no-op.

**Root cause:** `pr_exists()` only checks for *open* PRs. Once the
original bump PR merges, a retrigger sails past that guard,
`update_version_beat` correctly finds no diff and skips the commit, but
the script then unconditionally tries to push and `gh pr create` anyway.
A branch identical to its base has nothing to open a PR with, so GitHub
rejects it with "No commits between X and Y" and the script exits
non-zero.

Confirmed against the real repo state (`9.4`/`9.3`/`8.19` are already at
the reported versions, and their bump PRs are already merged) that this
is exactly the failure condition.

- Add a shared `no_new_commits()` helper to `common.sh`
- Use it in `bump-patch.sh` and `bump-minor.sh` to skip push/PR creation
cleanly (exit 0) when there's nothing to bump

## Test plan

- [x] Reproduced Julien's exact scenario for `9.4`→`9.4.4`,
`9.3`→`9.3.8`, `8.19`→`8.19.19` against the real branches — all three
now exit 0 with "already at X — nothing to bump" instead of failing
- [x] Verified a genuine new patch version (e.g. `9.4`→`9.4.5`) still
produces a commit and PR as before

Made with [Cursor](https://cursor.com)

Co-authored-by: Cloud Security Machine <cloudsecmachine@users.noreply.github.com>
Co-authored-by: Cursor <cursoragent@cursor.com>

9730 of 12836 relevant lines covered (75.8%)

16.43 hits per line

Jobs
ID Job ID Ran Files Coverage
1 28796306233.1 06 Jul 2026 02:03PM UTC 235
75.8
GitHub Action Run
Source Files on build 28796306233
  • Tree
  • List 235
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • b1914620 on github
  • Prev Build on gh-readonly-queue/main/pr-7185-19593ecfd803178856efb9990eab100b59a6ece8 (#28786161417)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc