Skip to content

fix(release): reconcile 0.6.0 metadata after image-alt merge - #147

Merged
seonghobae merged 2 commits into
mainfrom
fix/release-reconcile-image-alt
Aug 10, 2026
Merged

fix(release): reconcile 0.6.0 metadata after image-alt merge#147
seonghobae merged 2 commits into
mainfrom
fix/release-reconcile-image-alt

Conversation

@seonghobae

Copy link
Copy Markdown
Contributor

Purpose

Reconcile issue #118 after protected main advanced 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 any v0.6.0 promotion.

Test-first boundary

Exact protected base at branch creation: 3f3a319151aa811c492979465aff43f0e496d7d7.

RED head: ef8ba3181e5a9b5357e68938d5c370862c3c080e adds 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.

@coderabbitai

coderabbitai Bot commented Aug 10, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@seonghobae, you've reached your PR review limit, so we couldn't start this review.

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 @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 15bdf1fa-e7b0-4c77-a8ee-66a66c35fda5

📥 Commits

Reviewing files that changed from the base of the PR and between 3f3a319 and c56dfa3.

📒 Files selected for processing (2)
  • CHANGELOG.md
  • src/releaseCurrentMainAccessibility.test.ts

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@seonghobae
seonghobae marked this pull request as ready for review August 10, 2026 14:24
@seonghobae
seonghobae merged commit 50ac98c into main Aug 10, 2026
32 checks passed
@seonghobae
seonghobae deleted the fix/release-reconcile-image-alt branch August 10, 2026 14:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant