Skip to content

chore: remove release-as override now that v1.0.0 shipped - #83

Merged
grdsdev merged 1 commit into
mainfrom
chore/remove-release-as-override
Aug 12, 2026
Merged

chore: remove release-as override now that v1.0.0 shipped#83
grdsdev merged 1 commit into
mainfrom
chore/remove-release-as-override

Conversation

@grdsdev

@grdsdev grdsdev commented Aug 12, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Follow-up to chore: force initial release to 1.0.0 #82. The "release-as": "1.0.0" override was a one-time pin to force the first-ever release to 1.0.0 instead of the 2.0.0 that would otherwise be computed from #74's breaking change.
  • v1.0.0 has now shipped (chore(main): release 1.0.0 #81), so this override is removed. Future releases go back to normal semver computation from commit history.

Test plan

  • Merge this PR
  • Confirm the next release-please run computes a normal semver bump (not pinned)

The one-time pin added in #82 has served its purpose. Future releases
should go back to normal semver computation from commit history.
@grdsdev
grdsdev requested a review from a team as a code owner August 12, 2026 09:51
@coderabbitai

coderabbitai Bot commented Aug 12, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in: 52 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: 034a244b-adbc-42fb-938d-4a2bda95d2b3

📥 Commits

Reviewing files that changed from the base of the PR and between 93b5258 and 4868040.

📒 Files selected for processing (1)
  • release-please-config.json

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.

@grdsdev
grdsdev merged commit a827f14 into main Aug 12, 2026
2 checks passed
@grdsdev
grdsdev deleted the chore/remove-release-as-override branch August 12, 2026 10:22
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.

2 participants