Skip to content

Release 1.0.0-rc.2#47

Merged
tsouth89 merged 1 commit into
mainfrom
release/1.0.0-rc.2
Jul 18, 2026
Merged

Release 1.0.0-rc.2#47
tsouth89 merged 1 commit into
mainfrom
release/1.0.0-rc.2

Conversation

@tsouth89

Copy link
Copy Markdown
Owner

Version bump to 1.0.0-rc.2 across all locations (version.env build 92, both Cargo.tomls, package.json, tauri.conf.json, Cargo.lock) plus the changelog section.

Ships the three reviewed passes merged in #46:

  • Codex banked-reset display, including an explicit "0 available".
  • "Send test notification" button (real Windows toast pipeline).
  • Exact and Calm floating-bar information modes.
  • Explicit "unavailable" state for a limit window that drops out of a successful response.

After this merges and CI is green, an annotated v1.0.0-rc.2 tag will be pushed to trigger the signed-release workflow.

Bump MARKETING_VERSION/build and all package versions to 1.0.0-rc.2,
regenerate Cargo.lock, and add the changelog section for the banked-reset
display, test-notification button, Exact/Calm floating-bar modes, and the
explicit unavailable-window state.
@coderabbitai

coderabbitai Bot commented Jul 18, 2026

Copy link
Copy Markdown

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 8 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

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

Run ID: 0747c36a-f20f-4be8-8948-5f79fe398fbf

📥 Commits

Reviewing files that changed from the base of the PR and between 78537ef and 9917b67.

⛔ Files ignored due to path filters (1)
  • Cargo.lock is excluded by !**/*.lock
📒 Files selected for processing (6)
  • CHANGELOG.md
  • apps/desktop-tauri/package.json
  • apps/desktop-tauri/src-tauri/Cargo.toml
  • apps/desktop-tauri/src-tauri/tauri.conf.json
  • rust/Cargo.toml
  • version.env
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch release/1.0.0-rc.2

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

@cloudflare-workers-and-pages

Copy link
Copy Markdown
Contributor

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Preview URL Updated (UTC)
✅ Deployment successful!
View logs
ceiling 9917b67 Commit Preview URL

Branch Preview URL
Jul 18 2026, 01:52 AM

@tsouth89
tsouth89 merged commit 8bdccac into main Jul 18, 2026
6 checks passed
@tsouth89
tsouth89 deleted the release/1.0.0-rc.2 branch July 18, 2026 01:55
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