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

gsarantid / cloudbeat
76%
main: 76%

Build:
Build:
LAST BUILD BRANCH: fix-minor-bump-idempotency
DEFAULT BRANCH: main
Repo Added 06 Jul 2026 06:06PM UTC
Token 2VJJtwt89c3LBPhxCmTQYZeh57Z27XkgH regen
Build 10 Last
Files 245
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

LAST BUILD ON BRANCH fix-minor-bump-idempotency
branch: fix-minor-bump-idempotency
CHANGE BRANCH
x
Reset
Sync Branches
  • fix-minor-bump-idempotency
  • 9.5
  • bump-to-9.5.0
  • bump-to-9.6.0
  • bump-to-9.9.9
  • main
  • remove-mergify-version-bump-auto-merge

09 Jul 2026 08:25AM UTC coverage: 76.106%. Remained the same
29004734414

Pull #5

github

cloudsecmachine
fix: make bump-minor.sh idempotent on retrigger

When Nina retriggered the centralized version-bump pipeline yesterday
after our 9.5.0 bump had already succeeded, cloudbeat-version-bump #36
re-ran bump-minor.sh with the same env vars (NEW_VERSION=9.5.0). At that
point main was at 9.6.0 (from #7268), and the sed inside
update_version_beat happily rewrote version.go from 9.6.0 back to
9.5.0. The existing no_new_commits guard couldn't tell the difference
between "advance forward" and "regress backward" — it only asks "did
anything change vs main?" — so the regression commits passed the check
and the script pushed the resulting PR #7275 (now closed).

Two-layer fix:

1. bump-minor.sh: top-level guard. If main is already at
   next_minor_version(NEW_VERSION) (e.g. main=9.6.0 while
   NEW_VERSION=9.5.0), the entire bump has already completed. Exit 0
   before touching any files.

2. common.sh: new is_downgrade() helper (using sort -V so
   9.10.0 > 9.9.0 works correctly). update_version_beat and
   update_arm_templates now call it before writing: if the current
   value is >= the target, they refuse the write and log a clear
   message. Belt-and-suspenders — even if a caller forgets the
   top-level guard, no downgrade can escape the shared helper.

bump-patch.sh and post-minor-merge.sh are unchanged; patch bumps only
ever advance forward, and post-minor-merge is already idempotent via
its branch-exists check plus no_new_commits.

Co-authored-by: Cursor <cursoragent@cursor.com>
Pull Request #5: [fork smoke test] fix: make bump-minor.sh idempotent on retrigger

10205 of 13409 relevant lines covered (76.11%)

15.9 hits per line

Relevant lines Covered
Build:
Build:
13409 RELEVANT LINES 10205 COVERED LINES
15.9 HITS PER LINE
Source Files on fix-minor-bump-idempotency
  • Tree
  • List 245
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line

Recent builds

Builds Branch Commit Type Ran Committer Via Coverage
29004734414 fix-minor-bump-idempotency fix: make bump-minor.sh idempotent on retrigger When Nina retriggered the centralized version-bump pipeline yesterday after our 9.5.0 bump had already succeeded, cloudbeat-version-bump #36 re-ran bump-minor.sh with the same env vars (NEW_VERSION=... Pull #5 09 Jul 2026 08:44AM UTC cloudsecmachine github
76.11
See All Builds (10)

Badge your Repo: cloudbeat

We detected this repo isn’t badged! Grab the embed code to the right, add it to your repo to show off your code coverage, and when the badge is live hit the refresh button to remove this message.

Could not find badge in README.

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

Refresh
  • Settings
  • Repo on GitHub
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