chore(deps): bump @pymthouse/builder-sdk to 0.6.1#429
Conversation
Picks up the scoped fetchUsageForExternalUser fix (per-user userId on all three usage queries instead of an app-wide groupBy=user scan), resolving the production 503 on /api/v1/billing/pymthouse/usage for busy apps.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Review limit reached
Next review available in: 5 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (3)
📝 WalkthroughWalkthroughThe web application updates ChangesBuilder SDK update
Estimated code review effort: 1 (Trivial) | ~2 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
This commit updates the @pymthouse/builder-sdk dependency across multiple package.json files, replacing the previous pre-release version (0.6.1-rc.0) with the stable version (0.6.1). This change ensures compatibility and stability in the application.
|
@coderabbitai review |
✅ Action performedReview finished.
|
|
@seanhanca This is ready to merge, feel free to approve. I'm not able to merge due to coderabbit stuck |
Summary
@pymthouse/builder-sdkfrom0.6.0to0.6.1-rc.0inapps/web-next(dependency-only change).fetchUsageForExternalUserto run all three usage queries (user,pipeline_model,daily_pipeline) scoped withuserId, instead of starting from an app-widegroupBy=userscan and fanning out per end-user. On busy apps that scan intermittently 5xx'd upstream, which NaaP surfaced as a 503 onGET /api/v1/billing/pymthouse/usage?scope=me(prod issue forapp_98575870d7ae33589a3f0660). Mint was unaffected.Test plan
vitest— pymthouse usage route, adapter, and discovery-plans suites pass against the new SDK (37 tests)/api/v1/billing/pymthouse/usagestop after deploySummary by CodeRabbit