fix(release): reconcile 0.6.0 metadata after image-alt merge - #147
Conversation
|
Warning Review limit reached
Next review available in: 41 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Purpose
Reconcile issue #118 after protected
mainadvanced through #146. The protected 0.6.0 source candidate changed from the previously recorded generation, so the release metadata must acknowledge the newly protected explicit image alternative-text intent behavior before anyv0.6.0promotion.Test-first boundary
Exact protected base at branch creation:
3f3a319151aa811c492979465aff43f0e496d7d7.RED head:
ef8ba3181e5a9b5357e68938d5c370862c3c080eadds only a release-contract test. The test binds the already-protected toolbar behavior to a required 0.6.0 accessibility changelog statement and is expected to fail until the release metadata is reconciled.Scope
This lane changes only release evidence for already-protected behavior. It does not add product behavior, retag history, publish registries, weaken release gates, or alter the next-release DOCX page-layout Draft #141.