fix(ui): clarify private metadata OAuth consent copy#9226
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
🦋 Changeset detectedLatest commit: ed45b7b The changes in this PR will be included in the next version bump. This PR includes changesets to release 23 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Warning Review limit reached
Next review available in: 29 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: Repository YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (53)
Comment |
@clerk/astro
@clerk/backend
@clerk/chrome-extension
@clerk/clerk-js
@clerk/electron
@clerk/electron-passkeys
@clerk/eslint-plugin
@clerk/expo
@clerk/expo-google-signin
@clerk/expo-passkeys
@clerk/express
@clerk/fastify
@clerk/hono
@clerk/localizations
@clerk/nextjs
@clerk/nuxt
@clerk/react
@clerk/react-router
@clerk/shared
@clerk/tanstack-react-start
@clerk/testing
@clerk/ui
@clerk/upgrade
@clerk/vue
commit: |
API Changes Report
Summary
@clerk/sharedCurrent version: 4.25.7 Subpath
|
| ...item, | ||
| description: | ||
| item.scope === PRIVATE_METADATA_SCOPE | ||
| ? `Your private metadata set by ${applicationName}, which may include sensitive information` |
There was a problem hiding this comment.
Localized the private metadata scope description through oauthConsent.scopeList.privateMetadata, including the applicationName token and an override-focused component test. Addressed in 8e5b64e.
~ 🤖
6c32811 to
8e5b64e
Compare
Summary
Updates OAuth consent copy for the
private_metadatascope so users understand it may include sensitive information set by the Clerk application. The backend provides a safer generic description for older or non-Clerk consumers, while the official UI names the Clerk application directly. Consent-screen eligibility and authorization behavior are unchanged.Linear: https://linear.app/clerk/issue/USER-5731
Changes in this repo
Replaces the official consent UI description with a Clerk application-specific warning, adds focused component coverage, and includes the
@clerk/uipatch changeset.Companion PRs