Repository navigation
Upgrade Cloudflare OAuth provider to 0.8.2 - #843
Conversation
Adopt finite OAuth KV TTLs and scheduled purge, silence default onError console warnings, and keep malformed-client token exception coverage working under stricter auth-code validation.
|
Warning Review limit reached
Next review available in: 14 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: defaults Review profile: CHILL Plan: Pro Plus Run ID: β Files ignored due to path filters (1)
π Files selected for processing (4)
β¨ 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 |
|
π Preview deployed: https://kody-pr-843.kody-a99.workers.dev Worker: Mocks:
|
Summary
@cloudflare/workers-oauth-provider0.4.0 β 0.8.2Auth-affecting changes reviewed
purgeExpiredDataOAuthErrorresponsesgrantIdand stricter DCR URI validationKody uses the defaults and does not opt into EMA. Stable-account grant identity from #840 remains unchanged.
Validation
System recap β extends an existing primitive (medium risk)
Mode: recap Β· Base:
main@50ccd2f6Β· Head:e1e3d4c9Classification: extends β OAuth token/client lifetimes and cleanup behavior change under the current provider.
Primitives touched
scheduled-cronSystem map
MCP OAuth continues through the worker provider; scheduled cleanup removes expired KV state introduced by finite TTLs.
Legend: green = composes (wiring only) Β· amber = extended by this PR Β· red = new primitive Β· gray = context (unchanged, included only when an edge crosses it).
Invariants
Grant props still resolve stable per-user identity; no cross-user lookup path changes.