Skip to content

chore(main): release 0.54.0 - #757

Merged
gaborage merged 2 commits into
mainfrom
release-please--branches--main--components--go-bricks
Jul 24, 2026
Merged

chore(main): release 0.54.0#757
gaborage merged 2 commits into
mainfrom
release-please--branches--main--components--go-bricks

Conversation

@gaborage

@gaborage gaborage commented Jul 23, 2026

Copy link
Copy Markdown
Owner

🤖 I have created a release beep boop

0.54.0 (2026-07-24)

Added

  • outbox,inbox: shared control-plane ledger tenancy for dynamic multi-tenant deployments (#763) (d21ac0f)
  • server: fail fast on duplicate route registration (#761) (7dbc7e0)

Fixed

  • deps: update aws-sdk-go-v2 monorepo (#754) (7fe3c4d)
  • deps: update module github.com/gaborage/go-bricks to v0.53.0 (#755) (ca56b08)
  • deps: update module github.com/labstack/echo/v5 to v5.3.1 (#753) (fc1eb0d)

This PR was generated with Release Please. See documentation.

@coderabbitai

coderabbitai Bot commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

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: 31 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: Repository UI (base), Organization UI (inherited)

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 693bdd7c-184f-447e-ade4-ca3196c26362

📥 Commits

Reviewing files that changed from the base of the PR and between 24f1f3a and b2880d6.

📒 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--components--go-bricks

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

@gaborage
gaborage force-pushed the release-please--branches--main--components--go-bricks branch 2 times, most recently from 7538813 to 163cb4b Compare July 23, 2026 15:14
@gaborage gaborage changed the title chore(main): release 0.53.1 chore(main): release 0.54.0 Jul 23, 2026
@gaborage
gaborage force-pushed the release-please--branches--main--components--go-bricks branch from 163cb4b to deae6cb Compare July 23, 2026 17:24
@gaborage
gaborage force-pushed the release-please--branches--main--components--go-bricks branch from deae6cb to 286f1d0 Compare July 24, 2026 00:29
@gaborage
gaborage marked this pull request as ready for review July 24, 2026 06:38
@gaborage
gaborage merged commit 895c44f into main Jul 24, 2026
21 checks passed
@gaborage
gaborage deleted the release-please--branches--main--components--go-bricks branch July 24, 2026 06:39
@github-actions github-actions Bot added autorelease: tagged Release PR whose version has been tagged and published and removed autorelease: pending labels Jul 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

autorelease: tagged Release PR whose version has been tagged and published

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant