[MAINT]: Fix latent issue in JaCoCo badge update process #31
Description
Describe the need
So the timeline is:
| Date | Event |
|---|---|
| March 2 | "Protect main" ruleset created |
| March 9 | Ruleset updated (last modification) |
| March 11 | Last successful badge push — this means the pull_request rule may not have been in the ruleset until the March 9 update, or the March 11 push snuck through before the rule took full effect |
| March 17–22 | Runs on main succeeded because coverage didn't change, so git push was never attempted |
| March 25 | Your run had a coverage change → git push attempted → rejected |
The badge step was essentially a ticking time bomb — it only fails when coverage actually changes. Your smoke test changes are unrelated; they just happened to coincide with a run where the coverage percentage shifted (likely due to new/changed code on main), triggering the first push attempt since the ruleset locked down direct pushes.
SDK Version
0.1.32-java.0
Relevant log output
Code of Conduct
- I agree to follow this project's Code of Conduct
Metadata
Metadata
Assignees
Labels
No labels
Type
Fields
Give feedbackNo fields configured for Bug.