Conversation
|
Warning Review limit reached
More reviews will be available in 2 minutes and 51 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more credits in the billing tab to continue. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. Comment |
Greptile SummaryThis is a release PR bumping the version from
Confidence Score: 5/5Single-file version bump with no logic changes — safe to merge. The change is limited to incrementing the version string in the VERSION file from 1.0.2 to 1.1.0, which matches the described minor feature release. No code logic is modified. No files require special attention. Important Files Changed
Reviews (1): Last reviewed commit: "chore: release v1.1.0" | Re-trigger Greptile |
1.1.0 - 2026-06-11
Features
Note
Low Risk
Single-line version bump with no runtime or security impact; release tagging follows the existing automated workflow.
Overview
Release v1.1.0 — bumps the canonical version in
VERSIONfrom1.0.2to1.1.0, aligning the repo with the release PR workflow so merge can tagv1.1.0, refresh the major tag, and publish the GitHub release.This change does not alter application or action logic; it only updates the version source used by
scripts/postversion.shand the release automation described in the README.Reviewed by Cursor Bugbot for commit 0f36a91. Bugbot is set up for automated code reviews on this repo. Configure here.