Skip to content

chore(main): release 1.2.0 - #157

Merged
vovinacci merged 1 commit into
mainfrom
release-please--branches--main
Jul 21, 2026
Merged

chore(main): release 1.2.0#157
vovinacci merged 1 commit into
mainfrom
release-please--branches--main

Conversation

@vovinacci

@vovinacci vovinacci commented Jul 21, 2026

Copy link
Copy Markdown
Owner

🤖 I have created a release beep boop

1.2.0 (2026-07-21)

Features

  • backend: OpenTelemetry instrumentation with trace IDs in logs (#162) (23170c3)
  • backend: serve gRPC ItemService with event streaming (#161) (58fbd53)
  • backend: split health contract into /healthz and /readyz (#156) (8ab8006)
  • canary: Rust synthetic canary v1 behind synthetic profile (#159) (99d458a)
  • observability: add blackbox_exporter behind synthetic profile (#158) (a50785f)
  • proto: buf module with ItemService contract and CI gate (#160) (ebd57c1)

This PR was generated with Release Please. See documentation.

@vovinacci
vovinacci force-pushed the release-please--branches--main branch 4 times, most recently from 2982c44 to 2fc9929 Compare July 21, 2026 18:14
@coderabbitai

coderabbitai Bot commented Jul 21, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in: 53 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: e95f88c4-aa24-43e1-950e-b2e34fac003f

📥 Commits

Reviewing files that changed from the base of the PR and between 23170c3 and 06ffaed.

📒 Files selected for processing (2)
  • .release-please-manifest.json
  • CHANGELOG.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch release-please--branches--main

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.

@vovinacci
vovinacci force-pushed the release-please--branches--main branch from 2fc9929 to 06ffaed Compare July 21, 2026 19:03
@vovinacci
vovinacci merged commit e0ba952 into main Jul 21, 2026
7 checks passed
@vovinacci
vovinacci deleted the release-please--branches--main branch July 21, 2026 19:16
@vovinacci

Copy link
Copy Markdown
Owner Author

🤖 Created releases:

🌻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant