stacklok / toolhive / 24745833495 / 1
66%
main: 66%

DEFAULT BRANCH: main
Ran
Files 655
Run time 32s
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: 66.244% (+0.03%) from 66.21%
24745833495.1

push

github

web-flow 
Enforce v1beta1 API stability (#4991)

Flip the advisory CRD Schema Compatibility check (added in #4980 and
repaired in #4987) into an enforcing check, and document the contract.

Three pieces:

1. Workflow: drop continue-on-error, add an if: guard on the job that
   skips the check when the api-break-allowed label is applied. A
   skipped required-check counts as passing for branch protection, so
   the label is the only path through for an intentional break. Update
   the header comment and step summary heading to drop the "Phase 1:
   advisory" framing.

2. CONTRIBUTING.md: add a new "API Stability" top-level section with
   the v1beta1 stability contract (no field removal, type change,
   new required fields, validation narrowing, finalizer rename,
   spec.scope flip, un-serving a served version). Separate subsection
   documents the api-break-allowed escape hatch and the
   maintainer-coordination expectations.

3. PR template: add an "API Compatibility" section after Test plan
   that prompts contributors to describe the break + migration path
   when the label is applied. Section is standing (GitHub templates
   don't support conditional rendering) but the wording makes the
   N/A-for-non-breaking-PRs case explicit via the checkbox.

Post-merge maintainer actions (not code, can't be automated from a
PR): create the api-break-allowed GitHub label, and add "CRD Schema
Compatibility" to the required status checks in branch protection
for main.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

58588 of 88443 relevant lines covered (66.24%)

59.95 hits per line

Source Files on job 24745833495.1