Repository navigation
Conversation
Declared with a bang in the subject. Fixture only; close, never merge.
|
Warning Review limit reachedThe included review limit has been reached and this organization has disabled usage-based review continuation. Wait for reviews to reset or ask a billing admin to change After included review limits.
Reviews can continue after your included limit without a manual trigger. An admin must approve usage-based billing. Next included review available in 10 minutes. View limit details
Comment |
|
Note ✅ Breaking change approvedApproved by @ferr3ira-gabriel. 💥 The next release will be a major version. Gated by |
🔍 Lint Analysis
|
🔍 PR Validation Summary✅ PR Mergeable — no blocking failures
|
|
@coderabbitai review |
|
Description
Fixture 1 of 3 — approve this one. Opened to exercise the breaking-change gate on the post-#940 code. Not for merge: close it when the run is done.
The break is declared with a
!in the subject (feat(pr-validation)!:). Expected: the gate holds this at thebreaking-approvalEnvironment and asks for a decision.What to watch after approving:
breaking-changestays on the pull request — it is a fact, and approving does not make the break go awayawaiting-breaking-approvalcomes off — the decision is madeType of Change
test: Adding or updating testsBreaking Changes
Declared deliberately, to trip the gate. Nothing is released from a fixture branch.
Breaking change acknowledged: I understand that this PR intentionally introduces a breaking change and requires the next release to be a major version.
Testing
This is the test.
Related Issues
None.