chore(expo-passkeys): Add support for Expo 54 - #6752

Merged
wobsoriano merged 3 commits into
mainfrom
rob/passkey-expo-54
Sep 10, 2025
Merged

chore(expo-passkeys): Add support for Expo 54#6752
wobsoriano merged 3 commits into
mainfrom
rob/passkey-expo-54

Conversation

@wobsoriano

@wobsorianowobsoriano commented Sep 10, 2025

Copy link
Copy Markdown
Member

Description

Adjusts the expo peer dep to support Expo 54

https://expo.dev/changelog/sdk-54

Checklist

  • pnpm test runs as expected.
  • pnpm build runs as expected.
  • (If applicable) JSDoc comments have been added or updated for any package exports
  • (If applicable) Documentation has been updated

Type of change

  • 🐛 Bug fix
  • 🌟 New feature
  • 🔨 Breaking change
  • 📖 Refactoring / dependency upgrade / documentation
  • other:

Summary by CodeRabbit

  • New Features

    • Added compatibility with Expo 54, allowing the package to be used in projects targeting the latest Expo 54.x releases.
  • Chores

    • Updated peer dependency range to include Expo 54.x while maintaining exclusion of future major versions.
    • Added release metadata to publish a minor version update.

@vercel

vercelBot commented Sep 10, 2025

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

ProjectDeploymentPreviewCommentsUpdated (UTC)
clerk-js-sandboxReadyReadyPreviewCommentSep 10, 2025 9:21pm

@changeset-bot

changeset-botBot commented Sep 10, 2025

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 7f97749

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages
NameType
@clerk/expo-passkeysMinor
@clerk/clerk-expoPatch

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

@coderabbitai

coderabbitaiBot commented Sep 10, 2025

Copy link
Copy Markdown
Contributor

Walkthrough

Adjusts release metadata and broadens the Expo peer dependency for @clerk/expo-passkeys to include Expo 54.x by updating package.json. No source code or API changes.

Changes

Cohort / File(s)Summary of Changes
Release metadata
\.changeset/curly-plums-tease.md
Adds a changeset declaring a minor version bump for @clerk/expo-passkeys with note “Add support for Expo 54”.
Peer dependency range
packages/expo-passkeys/package.json
Expands expo peer dependency from ">=50 <54" to ">=50 <55" to allow Expo 54.x.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Pre-merge checks (3 passed)

✅ Passed checks (3 passed)
Check nameStatusExplanation
Description Check✅ PassedCheck skipped - CodeRabbit’s high-level summary is enabled.
Title Check✅ PassedThe title “chore(expo-passkeys): Add support for Expo 54” accurately reflects the primary change of updating the peer dependency range to include Expo SDK 54. It is concise, follows conventional commit style, and omits unnecessary detail or file lists. A reviewer scanning the history can immediately understand the purpose of the pull request.
Docstring Coverage✅ PassedNo functions found in the changes. Docstring coverage check skipped.

Poem

I twitch my whiskers, stamp with glee,
A semver hop—so light and free.
From 50 up to 54,
Our Expo path extends once more.
Carrot commits and version cheer,
Springy hops into the new frontier! 🥕🐇

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

  • Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
  • Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
pre_merge_checks:
custom_checks:
- name: "Undocumented Breaking Changes"mode: "warning"instructions: | Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch rob/passkey-expo-54

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

@pkg-pr-new

Copy link
Copy Markdown

Open in StackBlitz

@clerk/agent-toolkit

npm i https://pkg.pr.new/@clerk/agent-toolkit@6752

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@6752

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@6752

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@6752

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@6752

@clerk/dev-cli

npm i https://pkg.pr.new/@clerk/dev-cli@6752

@clerk/elements

npm i https://pkg.pr.new/@clerk/elements@6752

@clerk/clerk-expo

npm i https://pkg.pr.new/@clerk/clerk-expo@6752

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@6752

@clerk/express

npm i https://pkg.pr.new/@clerk/express@6752

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@6752

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@6752

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@6752

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@6752

@clerk/clerk-react

npm i https://pkg.pr.new/@clerk/clerk-react@6752

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@6752

@clerk/remix

npm i https://pkg.pr.new/@clerk/remix@6752

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@6752

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@6752

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@6752

@clerk/themes

npm i https://pkg.pr.new/@clerk/themes@6752

@clerk/types

npm i https://pkg.pr.new/@clerk/types@6752

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@6752

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@6752

commit: 7f97749

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (2)
.changeset/curly-plums-tease.md (1)

5-5: Nit: Make the entry a tad more explicit.

Consider “Add support for Expo SDK 54 (peer: expo >=50 <55)” for clearer release notes.

packages/expo-passkeys/package.json (1)

43-43: Bump devDependencies to Expo SDK 54 for coverage
DevDependencies in packages/expo-passkeys/package.json remain pinned to Expo ~52.0.47—update to ~54.0.0 (or add a CI matrix job for SDK 54) so local/CI tests cover the new range.

- "devDependencies": {- "expo": "~52.0.47"- },+ "devDependencies": {+ "expo": "~54.0.0"+ },
📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 82b84fe and 7f97749.

📒 Files selected for processing (2)
  • .changeset/curly-plums-tease.md (1 hunks)
  • packages/expo-passkeys/package.json (1 hunks)
🧰 Additional context used
📓 Path-based instructions (3)
**/*.{js,jsx,ts,tsx,json,css,scss,md,yaml,yml}

📄 CodeRabbit inference engine (.cursor/rules/development.mdc)

Use Prettier for consistent code formatting

Files:

  • packages/expo-passkeys/package.json
packages/*/package.json

📄 CodeRabbit inference engine (.cursor/rules/global.mdc)

All publishable packages should be placed under the packages/ directory

packages/*/package.json: All publishable packages must be located in the 'packages/' directory.
All packages must be published under the @clerk namespace on npm.
Semantic versioning must be used across all packages.

Files:

  • packages/expo-passkeys/package.json
.changeset/**

📄 CodeRabbit inference engine (.cursor/rules/monorepo.mdc)

Automated releases must use Changesets.

Files:

  • .changeset/curly-plums-tease.md
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (22)
  • GitHub Check: Integration Tests (billing, chrome)
  • GitHub Check: Integration Tests (custom, chrome)
  • GitHub Check: Integration Tests (nextjs, chrome, 14)
  • GitHub Check: Integration Tests (nextjs, chrome, 15)
  • GitHub Check: Integration Tests (machine, chrome)
  • GitHub Check: Integration Tests (tanstack-react-start, chrome)
  • GitHub Check: Integration Tests (nuxt, chrome)
  • GitHub Check: Integration Tests (vue, chrome)
  • GitHub Check: Integration Tests (expo-web, chrome)
  • GitHub Check: Integration Tests (react-router, chrome)
  • GitHub Check: Integration Tests (astro, chrome)
  • GitHub Check: Integration Tests (localhost, chrome)
  • GitHub Check: Integration Tests (quickstart, chrome)
  • GitHub Check: Integration Tests (ap-flows, chrome)
  • GitHub Check: Integration Tests (sessions, chrome)
  • GitHub Check: Integration Tests (elements, chrome)
  • GitHub Check: Integration Tests (express, chrome)
  • GitHub Check: Integration Tests (generic, chrome)
  • GitHub Check: Static analysis
  • GitHub Check: Unit Tests (22, **)
  • GitHub Check: semgrep-cloud-platform/scan
  • GitHub Check: semgrep-cloud-platform/scan
🔇 Additional comments (1)
.changeset/curly-plums-tease.md (1)

1-6: Changeset looks correct for a peer range expansion (minor bump).

Accurately communicates “Add support for Expo 54” and scopes a minor release for @clerk/expo-passkeys. No issues.

@wobsoriano
wobsoriano merged commit 720ca64 into mainSep 10, 2025
40 checks passed
@wobsoriano
wobsoriano deleted the rob/passkey-expo-54 branch September 10, 2025 22:13
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@wobsoriano@tmilewski@aeliox
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all
 blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
Skip to content

chore(expo-passkeys): Add support for Expo 54 - #6752

Merged
wobsoriano merged 3 commits into
mainfrom
rob/passkey-expo-54
Sep 10, 2025
Merged

chore(expo-passkeys): Add support for Expo 54#6752
wobsoriano merged 3 commits into
mainfrom
rob/passkey-expo-54

Conversation

@wobsoriano

@wobsorianowobsoriano commented Sep 10, 2025

Copy link
Copy Markdown
Member

Description

Adjusts the expo peer dep to support Expo 54

https://expo.dev/changelog/sdk-54

Checklist

  • pnpm test runs as expected.
  • pnpm build runs as expected.
  • (If applicable) JSDoc comments have been added or updated for any package exports
  • (If applicable) Documentation has been updated

Type of change

  • 🐛 Bug fix
  • 🌟 New feature
  • 🔨 Breaking change
  • 📖 Refactoring / dependency upgrade / documentation
  • other:

Summary by CodeRabbit

  • New Features

    • Added compatibility with Expo 54, allowing the package to be used in projects targeting the latest Expo 54.x releases.
  • Chores

    • Updated peer dependency range to include Expo 54.x while maintaining exclusion of future major versions.
    • Added release metadata to publish a minor version update.

@vercel

vercelBot commented Sep 10, 2025

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

ProjectDeploymentPreviewCommentsUpdated (UTC)
clerk-js-sandboxReadyReadyPreviewCommentSep 10, 2025 9:21pm

@changeset-bot

changeset-botBot commented Sep 10, 2025

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 7f97749

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages
NameType
@clerk/expo-passkeysMinor
@clerk/clerk-expoPatch

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

@coderabbitai

coderabbitaiBot commented Sep 10, 2025

Copy link
Copy Markdown
Contributor

Walkthrough

Adjusts release metadata and broadens the Expo peer dependency for @clerk/expo-passkeys to include Expo 54.x by updating package.json. No source code or API changes.

Changes

Cohort / File(s)Summary of Changes
Release metadata
\.changeset/curly-plums-tease.md
Adds a changeset declaring a minor version bump for @clerk/expo-passkeys with note “Add support for Expo 54”.
Peer dependency range
packages/expo-passkeys/package.json
Expands expo peer dependency from ">=50 <54" to ">=50 <55" to allow Expo 54.x.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Pre-merge checks (3 passed)

✅ Passed checks (3 passed)
Check nameStatusExplanation
Description Check✅ PassedCheck skipped - CodeRabbit’s high-level summary is enabled.
Title Check✅ PassedThe title “chore(expo-passkeys): Add support for Expo 54” accurately reflects the primary change of updating the peer dependency range to include Expo SDK 54. It is concise, follows conventional commit style, and omits unnecessary detail or file lists. A reviewer scanning the history can immediately understand the purpose of the pull request.
Docstring Coverage✅ PassedNo functions found in the changes. Docstring coverage check skipped.

Poem

I twitch my whiskers, stamp with glee,
A semver hop—so light and free.
From 50 up to 54,
Our Expo path extends once more.
Carrot commits and version cheer,
Springy hops into the new frontier! 🥕🐇

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

  • Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
  • Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
pre_merge_checks:
custom_checks:
- name: "Undocumented Breaking Changes"mode: "warning"instructions: | Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch rob/passkey-expo-54

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

@pkg-pr-new

Copy link
Copy Markdown

Open in StackBlitz

@clerk/agent-toolkit

npm i https://pkg.pr.new/@clerk/agent-toolkit@6752

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@6752

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@6752

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@6752

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@6752

@clerk/dev-cli

npm i https://pkg.pr.new/@clerk/dev-cli@6752

@clerk/elements

npm i https://pkg.pr.new/@clerk/elements@6752

@clerk/clerk-expo

npm i https://pkg.pr.new/@clerk/clerk-expo@6752

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@6752

@clerk/express

npm i https://pkg.pr.new/@clerk/express@6752

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@6752

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@6752

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@6752

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@6752

@clerk/clerk-react

npm i https://pkg.pr.new/@clerk/clerk-react@6752

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@6752

@clerk/remix

npm i https://pkg.pr.new/@clerk/remix@6752

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@6752

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@6752

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@6752

@clerk/themes

npm i https://pkg.pr.new/@clerk/themes@6752

@clerk/types

npm i https://pkg.pr.new/@clerk/types@6752

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@6752

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@6752

commit: 7f97749

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (2)
.changeset/curly-plums-tease.md (1)

5-5: Nit: Make the entry a tad more explicit.

Consider “Add support for Expo SDK 54 (peer: expo >=50 <55)” for clearer release notes.

packages/expo-passkeys/package.json (1)

43-43: Bump devDependencies to Expo SDK 54 for coverage
DevDependencies in packages/expo-passkeys/package.json remain pinned to Expo ~52.0.47—update to ~54.0.0 (or add a CI matrix job for SDK 54) so local/CI tests cover the new range.

- "devDependencies": {- "expo": "~52.0.47"- },+ "devDependencies": {+ "expo": "~54.0.0"+ },
📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 82b84fe and 7f97749.

📒 Files selected for processing (2)
  • .changeset/curly-plums-tease.md (1 hunks)
  • packages/expo-passkeys/package.json (1 hunks)
🧰 Additional context used
📓 Path-based instructions (3)
**/*.{js,jsx,ts,tsx,json,css,scss,md,yaml,yml}

📄 CodeRabbit inference engine (.cursor/rules/development.mdc)

Use Prettier for consistent code formatting

Files:

  • packages/expo-passkeys/package.json
packages/*/package.json

📄 CodeRabbit inference engine (.cursor/rules/global.mdc)

All publishable packages should be placed under the packages/ directory

packages/*/package.json: All publishable packages must be located in the 'packages/' directory.
All packages must be published under the @clerk namespace on npm.
Semantic versioning must be used across all packages.

Files:

  • packages/expo-passkeys/package.json
.changeset/**

📄 CodeRabbit inference engine (.cursor/rules/monorepo.mdc)

Automated releases must use Changesets.

Files:

  • .changeset/curly-plums-tease.md
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (22)
  • GitHub Check: Integration Tests (billing, chrome)
  • GitHub Check: Integration Tests (custom, chrome)
  • GitHub Check: Integration Tests (nextjs, chrome, 14)
  • GitHub Check: Integration Tests (nextjs, chrome, 15)
  • GitHub Check: Integration Tests (machine, chrome)
  • GitHub Check: Integration Tests (tanstack-react-start, chrome)
  • GitHub Check: Integration Tests (nuxt, chrome)
  • GitHub Check: Integration Tests (vue, chrome)
  • GitHub Check: Integration Tests (expo-web, chrome)
  • GitHub Check: Integration Tests (react-router, chrome)
  • GitHub Check: Integration Tests (astro, chrome)
  • GitHub Check: Integration Tests (localhost, chrome)
  • GitHub Check: Integration Tests (quickstart, chrome)
  • GitHub Check: Integration Tests (ap-flows, chrome)
  • GitHub Check: Integration Tests (sessions, chrome)
  • GitHub Check: Integration Tests (elements, chrome)
  • GitHub Check: Integration Tests (express, chrome)
  • GitHub Check: Integration Tests (generic, chrome)
  • GitHub Check: Static analysis
  • GitHub Check: Unit Tests (22, **)
  • GitHub Check: semgrep-cloud-platform/scan
  • GitHub Check: semgrep-cloud-platform/scan
🔇 Additional comments (1)
.changeset/curly-plums-tease.md (1)

1-6: Changeset looks correct for a peer range expansion (minor bump).

Accurately communicates “Add support for Expo 54” and scopes a minor release for @clerk/expo-passkeys. No issues.

@wobsoriano
wobsoriano merged commit 720ca64 into mainSep 10, 2025
40 checks passed
@wobsoriano
wobsoriano deleted the rob/passkey-expo-54 branch September 10, 2025 22:13
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@wobsoriano@tmilewski@aeliox
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix"); } } catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

chore(expo-passkeys): Add support for Expo 54 - #6752

Merged
wobsoriano merged 3 commits into
mainfrom
rob/passkey-expo-54
Sep 10, 2025
Merged

chore(expo-passkeys): Add support for Expo 54#6752
wobsoriano merged 3 commits into
mainfrom
rob/passkey-expo-54

Conversation

@wobsoriano

@wobsorianowobsoriano commented Sep 10, 2025

Copy link
Copy Markdown
Member

Description

Adjusts the expo peer dep to support Expo 54

https://expo.dev/changelog/sdk-54

Checklist

  • pnpm test runs as expected.
  • pnpm build runs as expected.
  • (If applicable) JSDoc comments have been added or updated for any package exports
  • (If applicable) Documentation has been updated

Type of change

  • 🐛 Bug fix
  • 🌟 New feature
  • 🔨 Breaking change
  • 📖 Refactoring / dependency upgrade / documentation
  • other:

Summary by CodeRabbit

  • New Features

    • Added compatibility with Expo 54, allowing the package to be used in projects targeting the latest Expo 54.x releases.
  • Chores

    • Updated peer dependency range to include Expo 54.x while maintaining exclusion of future major versions.
    • Added release metadata to publish a minor version update.

@vercel

vercelBot commented Sep 10, 2025

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

ProjectDeploymentPreviewCommentsUpdated (UTC)
clerk-js-sandboxReadyReadyPreviewCommentSep 10, 2025 9:21pm

@changeset-bot

changeset-botBot commented Sep 10, 2025

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 7f97749

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages
NameType
@clerk/expo-passkeysMinor
@clerk/clerk-expoPatch

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

@coderabbitai

coderabbitaiBot commented Sep 10, 2025

Copy link
Copy Markdown
Contributor

Walkthrough

Adjusts release metadata and broadens the Expo peer dependency for @clerk/expo-passkeys to include Expo 54.x by updating package.json. No source code or API changes.

Changes

Cohort / File(s)Summary of Changes
Release metadata
\.changeset/curly-plums-tease.md
Adds a changeset declaring a minor version bump for @clerk/expo-passkeys with note “Add support for Expo 54”.
Peer dependency range
packages/expo-passkeys/package.json
Expands expo peer dependency from ">=50 <54" to ">=50 <55" to allow Expo 54.x.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Pre-merge checks (3 passed)

✅ Passed checks (3 passed)
Check nameStatusExplanation
Description Check✅ PassedCheck skipped - CodeRabbit’s high-level summary is enabled.
Title Check✅ PassedThe title “chore(expo-passkeys): Add support for Expo 54” accurately reflects the primary change of updating the peer dependency range to include Expo SDK 54. It is concise, follows conventional commit style, and omits unnecessary detail or file lists. A reviewer scanning the history can immediately understand the purpose of the pull request.
Docstring Coverage✅ PassedNo functions found in the changes. Docstring coverage check skipped.

Poem

I twitch my whiskers, stamp with glee,
A semver hop—so light and free.
From 50 up to 54,
Our Expo path extends once more.
Carrot commits and version cheer,
Springy hops into the new frontier! 🥕🐇

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

  • Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
  • Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
pre_merge_checks:
custom_checks:
- name: "Undocumented Breaking Changes"mode: "warning"instructions: | Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch rob/passkey-expo-54

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

@pkg-pr-new

Copy link
Copy Markdown

Open in StackBlitz

@clerk/agent-toolkit

npm i https://pkg.pr.new/@clerk/agent-toolkit@6752

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@6752

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@6752

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@6752

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@6752

@clerk/dev-cli

npm i https://pkg.pr.new/@clerk/dev-cli@6752

@clerk/elements

npm i https://pkg.pr.new/@clerk/elements@6752

@clerk/clerk-expo

npm i https://pkg.pr.new/@clerk/clerk-expo@6752

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@6752

@clerk/express

npm i https://pkg.pr.new/@clerk/express@6752

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@6752

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@6752

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@6752

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@6752

@clerk/clerk-react

npm i https://pkg.pr.new/@clerk/clerk-react@6752

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@6752

@clerk/remix

npm i https://pkg.pr.new/@clerk/remix@6752

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@6752

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@6752

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@6752

@clerk/themes

npm i https://pkg.pr.new/@clerk/themes@6752

@clerk/types

npm i https://pkg.pr.new/@clerk/types@6752

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@6752

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@6752

commit: 7f97749

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (2)
.changeset/curly-plums-tease.md (1)

5-5: Nit: Make the entry a tad more explicit.

Consider “Add support for Expo SDK 54 (peer: expo >=50 <55)” for clearer release notes.

packages/expo-passkeys/package.json (1)

43-43: Bump devDependencies to Expo SDK 54 for coverage
DevDependencies in packages/expo-passkeys/package.json remain pinned to Expo ~52.0.47—update to ~54.0.0 (or add a CI matrix job for SDK 54) so local/CI tests cover the new range.

- "devDependencies": {- "expo": "~52.0.47"- },+ "devDependencies": {+ "expo": "~54.0.0"+ },
📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 82b84fe and 7f97749.

📒 Files selected for processing (2)
  • .changeset/curly-plums-tease.md (1 hunks)
  • packages/expo-passkeys/package.json (1 hunks)
🧰 Additional context used
📓 Path-based instructions (3)
**/*.{js,jsx,ts,tsx,json,css,scss,md,yaml,yml}

📄 CodeRabbit inference engine (.cursor/rules/development.mdc)

Use Prettier for consistent code formatting

Files:

  • packages/expo-passkeys/package.json
packages/*/package.json

📄 CodeRabbit inference engine (.cursor/rules/global.mdc)

All publishable packages should be placed under the packages/ directory

packages/*/package.json: All publishable packages must be located in the 'packages/' directory.
All packages must be published under the @clerk namespace on npm.
Semantic versioning must be used across all packages.

Files:

  • packages/expo-passkeys/package.json
.changeset/**

📄 CodeRabbit inference engine (.cursor/rules/monorepo.mdc)

Automated releases must use Changesets.

Files:

  • .changeset/curly-plums-tease.md
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (22)
  • GitHub Check: Integration Tests (billing, chrome)
  • GitHub Check: Integration Tests (custom, chrome)
  • GitHub Check: Integration Tests (nextjs, chrome, 14)
  • GitHub Check: Integration Tests (nextjs, chrome, 15)
  • GitHub Check: Integration Tests (machine, chrome)
  • GitHub Check: Integration Tests (tanstack-react-start, chrome)
  • GitHub Check: Integration Tests (nuxt, chrome)
  • GitHub Check: Integration Tests (vue, chrome)
  • GitHub Check: Integration Tests (expo-web, chrome)
  • GitHub Check: Integration Tests (react-router, chrome)
  • GitHub Check: Integration Tests (astro, chrome)
  • GitHub Check: Integration Tests (localhost, chrome)
  • GitHub Check: Integration Tests (quickstart, chrome)
  • GitHub Check: Integration Tests (ap-flows, chrome)
  • GitHub Check: Integration Tests (sessions, chrome)
  • GitHub Check: Integration Tests (elements, chrome)
  • GitHub Check: Integration Tests (express, chrome)
  • GitHub Check: Integration Tests (generic, chrome)
  • GitHub Check: Static analysis
  • GitHub Check: Unit Tests (22, **)
  • GitHub Check: semgrep-cloud-platform/scan
  • GitHub Check: semgrep-cloud-platform/scan
🔇 Additional comments (1)
.changeset/curly-plums-tease.md (1)

1-6: Changeset looks correct for a peer range expansion (minor bump).

Accurately communicates “Add support for Expo 54” and scopes a minor release for @clerk/expo-passkeys. No issues.

@wobsoriano
wobsoriano merged commit 720ca64 into mainSep 10, 2025
40 checks passed
@wobsoriano
wobsoriano deleted the rob/passkey-expo-54 branch September 10, 2025 22:13
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@wobsoriano@tmilewski@aeliox
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length > 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms"); } } catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

chore(expo-passkeys): Add support for Expo 54 - #6752

Merged
wobsoriano merged 3 commits into
mainfrom
rob/passkey-expo-54
Sep 10, 2025
Merged

chore(expo-passkeys): Add support for Expo 54#6752
wobsoriano merged 3 commits into
mainfrom
rob/passkey-expo-54

Conversation

@wobsoriano

@wobsorianowobsoriano commented Sep 10, 2025

Copy link
Copy Markdown
Member

Description

Adjusts the expo peer dep to support Expo 54

https://expo.dev/changelog/sdk-54

Checklist

  • pnpm test runs as expected.
  • pnpm build runs as expected.
  • (If applicable) JSDoc comments have been added or updated for any package exports
  • (If applicable) Documentation has been updated

Type of change

  • 🐛 Bug fix
  • 🌟 New feature
  • 🔨 Breaking change
  • 📖 Refactoring / dependency upgrade / documentation
  • other:

Summary by CodeRabbit

  • New Features

    • Added compatibility with Expo 54, allowing the package to be used in projects targeting the latest Expo 54.x releases.
  • Chores

    • Updated peer dependency range to include Expo 54.x while maintaining exclusion of future major versions.
    • Added release metadata to publish a minor version update.

@vercel

vercelBot commented Sep 10, 2025

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

ProjectDeploymentPreviewCommentsUpdated (UTC)
clerk-js-sandboxReadyReadyPreviewCommentSep 10, 2025 9:21pm

@changeset-bot

changeset-botBot commented Sep 10, 2025

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 7f97749

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages
NameType
@clerk/expo-passkeysMinor
@clerk/clerk-expoPatch

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

@coderabbitai

coderabbitaiBot commented Sep 10, 2025

Copy link
Copy Markdown
Contributor

Walkthrough

Adjusts release metadata and broadens the Expo peer dependency for @clerk/expo-passkeys to include Expo 54.x by updating package.json. No source code or API changes.

Changes

Cohort / File(s)Summary of Changes
Release metadata
\.changeset/curly-plums-tease.md
Adds a changeset declaring a minor version bump for @clerk/expo-passkeys with note “Add support for Expo 54”.
Peer dependency range
packages/expo-passkeys/package.json
Expands expo peer dependency from ">=50 <54" to ">=50 <55" to allow Expo 54.x.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Pre-merge checks (3 passed)

✅ Passed checks (3 passed)
Check nameStatusExplanation
Description Check✅ PassedCheck skipped - CodeRabbit’s high-level summary is enabled.
Title Check✅ PassedThe title “chore(expo-passkeys): Add support for Expo 54” accurately reflects the primary change of updating the peer dependency range to include Expo SDK 54. It is concise, follows conventional commit style, and omits unnecessary detail or file lists. A reviewer scanning the history can immediately understand the purpose of the pull request.
Docstring Coverage✅ PassedNo functions found in the changes. Docstring coverage check skipped.

Poem

I twitch my whiskers, stamp with glee,
A semver hop—so light and free.
From 50 up to 54,
Our Expo path extends once more.
Carrot commits and version cheer,
Springy hops into the new frontier! 🥕🐇

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

  • Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
  • Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
pre_merge_checks:
custom_checks:
- name: "Undocumented Breaking Changes"mode: "warning"instructions: | Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch rob/passkey-expo-54

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

@pkg-pr-new

Copy link
Copy Markdown

Open in StackBlitz

@clerk/agent-toolkit

npm i https://pkg.pr.new/@clerk/agent-toolkit@6752

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@6752

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@6752

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@6752

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@6752

@clerk/dev-cli

npm i https://pkg.pr.new/@clerk/dev-cli@6752

@clerk/elements

npm i https://pkg.pr.new/@clerk/elements@6752

@clerk/clerk-expo

npm i https://pkg.pr.new/@clerk/clerk-expo@6752

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@6752

@clerk/express

npm i https://pkg.pr.new/@clerk/express@6752

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@6752

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@6752

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@6752

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@6752

@clerk/clerk-react

npm i https://pkg.pr.new/@clerk/clerk-react@6752

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@6752

@clerk/remix

npm i https://pkg.pr.new/@clerk/remix@6752

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@6752

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@6752

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@6752

@clerk/themes

npm i https://pkg.pr.new/@clerk/themes@6752

@clerk/types

npm i https://pkg.pr.new/@clerk/types@6752

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@6752

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@6752

commit: 7f97749

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (2)
.changeset/curly-plums-tease.md (1)

5-5: Nit: Make the entry a tad more explicit.

Consider “Add support for Expo SDK 54 (peer: expo >=50 <55)” for clearer release notes.

packages/expo-passkeys/package.json (1)

43-43: Bump devDependencies to Expo SDK 54 for coverage
DevDependencies in packages/expo-passkeys/package.json remain pinned to Expo ~52.0.47—update to ~54.0.0 (or add a CI matrix job for SDK 54) so local/CI tests cover the new range.

- "devDependencies": {- "expo": "~52.0.47"- },+ "devDependencies": {+ "expo": "~54.0.0"+ },
📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 82b84fe and 7f97749.

📒 Files selected for processing (2)
  • .changeset/curly-plums-tease.md (1 hunks)
  • packages/expo-passkeys/package.json (1 hunks)
🧰 Additional context used
📓 Path-based instructions (3)
**/*.{js,jsx,ts,tsx,json,css,scss,md,yaml,yml}

📄 CodeRabbit inference engine (.cursor/rules/development.mdc)

Use Prettier for consistent code formatting

Files:

  • packages/expo-passkeys/package.json
packages/*/package.json

📄 CodeRabbit inference engine (.cursor/rules/global.mdc)

All publishable packages should be placed under the packages/ directory

packages/*/package.json: All publishable packages must be located in the 'packages/' directory.
All packages must be published under the @clerk namespace on npm.
Semantic versioning must be used across all packages.

Files:

  • packages/expo-passkeys/package.json
.changeset/**

📄 CodeRabbit inference engine (.cursor/rules/monorepo.mdc)

Automated releases must use Changesets.

Files:

  • .changeset/curly-plums-tease.md
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (22)
  • GitHub Check: Integration Tests (billing, chrome)
  • GitHub Check: Integration Tests (custom, chrome)
  • GitHub Check: Integration Tests (nextjs, chrome, 14)
  • GitHub Check: Integration Tests (nextjs, chrome, 15)
  • GitHub Check: Integration Tests (machine, chrome)
  • GitHub Check: Integration Tests (tanstack-react-start, chrome)
  • GitHub Check: Integration Tests (nuxt, chrome)
  • GitHub Check: Integration Tests (vue, chrome)
  • GitHub Check: Integration Tests (expo-web, chrome)
  • GitHub Check: Integration Tests (react-router, chrome)
  • GitHub Check: Integration Tests (astro, chrome)
  • GitHub Check: Integration Tests (localhost, chrome)
  • GitHub Check: Integration Tests (quickstart, chrome)
  • GitHub Check: Integration Tests (ap-flows, chrome)
  • GitHub Check: Integration Tests (sessions, chrome)
  • GitHub Check: Integration Tests (elements, chrome)
  • GitHub Check: Integration Tests (express, chrome)
  • GitHub Check: Integration Tests (generic, chrome)
  • GitHub Check: Static analysis
  • GitHub Check: Unit Tests (22, **)
  • GitHub Check: semgrep-cloud-platform/scan
  • GitHub Check: semgrep-cloud-platform/scan
🔇 Additional comments (1)
.changeset/curly-plums-tease.md (1)

1-6: Changeset looks correct for a peer range expansion (minor bump).

Accurately communicates “Add support for Expo 54” and scopes a minor release for @clerk/expo-passkeys. No issues.

@wobsoriano
wobsoriano merged commit 720ca64 into mainSep 10, 2025
40 checks passed
@wobsoriano
wobsoriano deleted the rob/passkey-expo-54 branch September 10, 2025 22:13
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@wobsoriano@tmilewski@aeliox
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links"); } } catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); } })(); (function(){ try { var __m = "youtube.com"; var __re = new RegExp('^' + "youtube\\.com" + '
Skip to content

chore(expo-passkeys): Add support for Expo 54 - #6752

Merged
wobsoriano merged 3 commits into
mainfrom
rob/passkey-expo-54
Sep 10, 2025
Merged

chore(expo-passkeys): Add support for Expo 54#6752
wobsoriano merged 3 commits into
mainfrom
rob/passkey-expo-54

Conversation

@wobsoriano

@wobsorianowobsoriano commented Sep 10, 2025

Copy link
Copy Markdown
Member

Description

Adjusts the expo peer dep to support Expo 54

https://expo.dev/changelog/sdk-54

Checklist

  • pnpm test runs as expected.
  • pnpm build runs as expected.
  • (If applicable) JSDoc comments have been added or updated for any package exports
  • (If applicable) Documentation has been updated

Type of change

  • 🐛 Bug fix
  • 🌟 New feature
  • 🔨 Breaking change
  • 📖 Refactoring / dependency upgrade / documentation
  • other:

Summary by CodeRabbit

  • New Features

    • Added compatibility with Expo 54, allowing the package to be used in projects targeting the latest Expo 54.x releases.
  • Chores

    • Updated peer dependency range to include Expo 54.x while maintaining exclusion of future major versions.
    • Added release metadata to publish a minor version update.

@vercel

vercelBot commented Sep 10, 2025

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

ProjectDeploymentPreviewCommentsUpdated (UTC)
clerk-js-sandboxReadyReadyPreviewCommentSep 10, 2025 9:21pm

@changeset-bot

changeset-botBot commented Sep 10, 2025

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 7f97749

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages
NameType
@clerk/expo-passkeysMinor
@clerk/clerk-expoPatch

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

@coderabbitai

coderabbitaiBot commented Sep 10, 2025

Copy link
Copy Markdown
Contributor

Walkthrough

Adjusts release metadata and broadens the Expo peer dependency for @clerk/expo-passkeys to include Expo 54.x by updating package.json. No source code or API changes.

Changes

Cohort / File(s)Summary of Changes
Release metadata
\.changeset/curly-plums-tease.md
Adds a changeset declaring a minor version bump for @clerk/expo-passkeys with note “Add support for Expo 54”.
Peer dependency range
packages/expo-passkeys/package.json
Expands expo peer dependency from ">=50 <54" to ">=50 <55" to allow Expo 54.x.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Pre-merge checks (3 passed)

✅ Passed checks (3 passed)
Check nameStatusExplanation
Description Check✅ PassedCheck skipped - CodeRabbit’s high-level summary is enabled.
Title Check✅ PassedThe title “chore(expo-passkeys): Add support for Expo 54” accurately reflects the primary change of updating the peer dependency range to include Expo SDK 54. It is concise, follows conventional commit style, and omits unnecessary detail or file lists. A reviewer scanning the history can immediately understand the purpose of the pull request.
Docstring Coverage✅ PassedNo functions found in the changes. Docstring coverage check skipped.

Poem

I twitch my whiskers, stamp with glee,
A semver hop—so light and free.
From 50 up to 54,
Our Expo path extends once more.
Carrot commits and version cheer,
Springy hops into the new frontier! 🥕🐇

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

  • Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
  • Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
pre_merge_checks:
custom_checks:
- name: "Undocumented Breaking Changes"mode: "warning"instructions: | Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch rob/passkey-expo-54

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

@pkg-pr-new

Copy link
Copy Markdown

Open in StackBlitz

@clerk/agent-toolkit

npm i https://pkg.pr.new/@clerk/agent-toolkit@6752

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@6752

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@6752

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@6752

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@6752

@clerk/dev-cli

npm i https://pkg.pr.new/@clerk/dev-cli@6752

@clerk/elements

npm i https://pkg.pr.new/@clerk/elements@6752

@clerk/clerk-expo

npm i https://pkg.pr.new/@clerk/clerk-expo@6752

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@6752

@clerk/express

npm i https://pkg.pr.new/@clerk/express@6752

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@6752

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@6752

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@6752

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@6752

@clerk/clerk-react

npm i https://pkg.pr.new/@clerk/clerk-react@6752

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@6752

@clerk/remix

npm i https://pkg.pr.new/@clerk/remix@6752

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@6752

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@6752

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@6752

@clerk/themes

npm i https://pkg.pr.new/@clerk/themes@6752

@clerk/types

npm i https://pkg.pr.new/@clerk/types@6752

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@6752

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@6752

commit: 7f97749

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (2)
.changeset/curly-plums-tease.md (1)

5-5: Nit: Make the entry a tad more explicit.

Consider “Add support for Expo SDK 54 (peer: expo >=50 <55)” for clearer release notes.

packages/expo-passkeys/package.json (1)

43-43: Bump devDependencies to Expo SDK 54 for coverage
DevDependencies in packages/expo-passkeys/package.json remain pinned to Expo ~52.0.47—update to ~54.0.0 (or add a CI matrix job for SDK 54) so local/CI tests cover the new range.

- "devDependencies": {- "expo": "~52.0.47"- },+ "devDependencies": {+ "expo": "~54.0.0"+ },
📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 82b84fe and 7f97749.

📒 Files selected for processing (2)
  • .changeset/curly-plums-tease.md (1 hunks)
  • packages/expo-passkeys/package.json (1 hunks)
🧰 Additional context used
📓 Path-based instructions (3)
**/*.{js,jsx,ts,tsx,json,css,scss,md,yaml,yml}

📄 CodeRabbit inference engine (.cursor/rules/development.mdc)

Use Prettier for consistent code formatting

Files:

  • packages/expo-passkeys/package.json
packages/*/package.json

📄 CodeRabbit inference engine (.cursor/rules/global.mdc)

All publishable packages should be placed under the packages/ directory

packages/*/package.json: All publishable packages must be located in the 'packages/' directory.
All packages must be published under the @clerk namespace on npm.
Semantic versioning must be used across all packages.

Files:

  • packages/expo-passkeys/package.json
.changeset/**

📄 CodeRabbit inference engine (.cursor/rules/monorepo.mdc)

Automated releases must use Changesets.

Files:

  • .changeset/curly-plums-tease.md
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (22)
  • GitHub Check: Integration Tests (billing, chrome)
  • GitHub Check: Integration Tests (custom, chrome)
  • GitHub Check: Integration Tests (nextjs, chrome, 14)
  • GitHub Check: Integration Tests (nextjs, chrome, 15)
  • GitHub Check: Integration Tests (machine, chrome)
  • GitHub Check: Integration Tests (tanstack-react-start, chrome)
  • GitHub Check: Integration Tests (nuxt, chrome)
  • GitHub Check: Integration Tests (vue, chrome)
  • GitHub Check: Integration Tests (expo-web, chrome)
  • GitHub Check: Integration Tests (react-router, chrome)
  • GitHub Check: Integration Tests (astro, chrome)
  • GitHub Check: Integration Tests (localhost, chrome)
  • GitHub Check: Integration Tests (quickstart, chrome)
  • GitHub Check: Integration Tests (ap-flows, chrome)
  • GitHub Check: Integration Tests (sessions, chrome)
  • GitHub Check: Integration Tests (elements, chrome)
  • GitHub Check: Integration Tests (express, chrome)
  • GitHub Check: Integration Tests (generic, chrome)
  • GitHub Check: Static analysis
  • GitHub Check: Unit Tests (22, **)
  • GitHub Check: semgrep-cloud-platform/scan
  • GitHub Check: semgrep-cloud-platform/scan
🔇 Additional comments (1)
.changeset/curly-plums-tease.md (1)

1-6: Changeset looks correct for a peer range expansion (minor bump).

Accurately communicates “Add support for Expo 54” and scopes a minor release for @clerk/expo-passkeys. No issues.

@wobsoriano
wobsoriano merged commit 720ca64 into mainSep 10, 2025
40 checks passed
@wobsoriano
wobsoriano deleted the rob/passkey-expo-54 branch September 10, 2025 22:13
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@wobsoriano@tmilewski@aeliox
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default"); } } catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

chore(expo-passkeys): Add support for Expo 54 - #6752

Merged
wobsoriano merged 3 commits into
mainfrom
rob/passkey-expo-54
Sep 10, 2025
Merged

chore(expo-passkeys): Add support for Expo 54#6752
wobsoriano merged 3 commits into
mainfrom
rob/passkey-expo-54

Conversation

@wobsoriano

@wobsorianowobsoriano commented Sep 10, 2025

Copy link
Copy Markdown
Member

Description

Adjusts the expo peer dep to support Expo 54

https://expo.dev/changelog/sdk-54

Checklist

  • pnpm test runs as expected.
  • pnpm build runs as expected.
  • (If applicable) JSDoc comments have been added or updated for any package exports
  • (If applicable) Documentation has been updated

Type of change

  • 🐛 Bug fix
  • 🌟 New feature
  • 🔨 Breaking change
  • 📖 Refactoring / dependency upgrade / documentation
  • other:

Summary by CodeRabbit

  • New Features

    • Added compatibility with Expo 54, allowing the package to be used in projects targeting the latest Expo 54.x releases.
  • Chores

    • Updated peer dependency range to include Expo 54.x while maintaining exclusion of future major versions.
    • Added release metadata to publish a minor version update.

@vercel

vercelBot commented Sep 10, 2025

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

ProjectDeploymentPreviewCommentsUpdated (UTC)
clerk-js-sandboxReadyReadyPreviewCommentSep 10, 2025 9:21pm

@changeset-bot

changeset-botBot commented Sep 10, 2025

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 7f97749

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages
NameType
@clerk/expo-passkeysMinor
@clerk/clerk-expoPatch

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

@coderabbitai

coderabbitaiBot commented Sep 10, 2025

Copy link
Copy Markdown
Contributor

Walkthrough

Adjusts release metadata and broadens the Expo peer dependency for @clerk/expo-passkeys to include Expo 54.x by updating package.json. No source code or API changes.

Changes

Cohort / File(s)Summary of Changes
Release metadata
\.changeset/curly-plums-tease.md
Adds a changeset declaring a minor version bump for @clerk/expo-passkeys with note “Add support for Expo 54”.
Peer dependency range
packages/expo-passkeys/package.json
Expands expo peer dependency from ">=50 <54" to ">=50 <55" to allow Expo 54.x.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Pre-merge checks (3 passed)

✅ Passed checks (3 passed)
Check nameStatusExplanation
Description Check✅ PassedCheck skipped - CodeRabbit’s high-level summary is enabled.
Title Check✅ PassedThe title “chore(expo-passkeys): Add support for Expo 54” accurately reflects the primary change of updating the peer dependency range to include Expo SDK 54. It is concise, follows conventional commit style, and omits unnecessary detail or file lists. A reviewer scanning the history can immediately understand the purpose of the pull request.
Docstring Coverage✅ PassedNo functions found in the changes. Docstring coverage check skipped.

Poem

I twitch my whiskers, stamp with glee,
A semver hop—so light and free.
From 50 up to 54,
Our Expo path extends once more.
Carrot commits and version cheer,
Springy hops into the new frontier! 🥕🐇

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

  • Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
  • Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
pre_merge_checks:
custom_checks:
- name: "Undocumented Breaking Changes"mode: "warning"instructions: | Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch rob/passkey-expo-54

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

@pkg-pr-new

Copy link
Copy Markdown

Open in StackBlitz

@clerk/agent-toolkit

npm i https://pkg.pr.new/@clerk/agent-toolkit@6752

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@6752

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@6752

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@6752

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@6752

@clerk/dev-cli

npm i https://pkg.pr.new/@clerk/dev-cli@6752

@clerk/elements

npm i https://pkg.pr.new/@clerk/elements@6752

@clerk/clerk-expo

npm i https://pkg.pr.new/@clerk/clerk-expo@6752

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@6752

@clerk/express

npm i https://pkg.pr.new/@clerk/express@6752

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@6752

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@6752

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@6752

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@6752

@clerk/clerk-react

npm i https://pkg.pr.new/@clerk/clerk-react@6752

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@6752

@clerk/remix

npm i https://pkg.pr.new/@clerk/remix@6752

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@6752

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@6752

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@6752

@clerk/themes

npm i https://pkg.pr.new/@clerk/themes@6752

@clerk/types

npm i https://pkg.pr.new/@clerk/types@6752

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@6752

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@6752

commit: 7f97749

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (2)
.changeset/curly-plums-tease.md (1)

5-5: Nit: Make the entry a tad more explicit.

Consider “Add support for Expo SDK 54 (peer: expo >=50 <55)” for clearer release notes.

packages/expo-passkeys/package.json (1)

43-43: Bump devDependencies to Expo SDK 54 for coverage
DevDependencies in packages/expo-passkeys/package.json remain pinned to Expo ~52.0.47—update to ~54.0.0 (or add a CI matrix job for SDK 54) so local/CI tests cover the new range.

- "devDependencies": {- "expo": "~52.0.47"- },+ "devDependencies": {+ "expo": "~54.0.0"+ },
📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 82b84fe and 7f97749.

📒 Files selected for processing (2)
  • .changeset/curly-plums-tease.md (1 hunks)
  • packages/expo-passkeys/package.json (1 hunks)
🧰 Additional context used
📓 Path-based instructions (3)
**/*.{js,jsx,ts,tsx,json,css,scss,md,yaml,yml}

📄 CodeRabbit inference engine (.cursor/rules/development.mdc)

Use Prettier for consistent code formatting

Files:

  • packages/expo-passkeys/package.json
packages/*/package.json

📄 CodeRabbit inference engine (.cursor/rules/global.mdc)

All publishable packages should be placed under the packages/ directory

packages/*/package.json: All publishable packages must be located in the 'packages/' directory.
All packages must be published under the @clerk namespace on npm.
Semantic versioning must be used across all packages.

Files:

  • packages/expo-passkeys/package.json
.changeset/**

📄 CodeRabbit inference engine (.cursor/rules/monorepo.mdc)

Automated releases must use Changesets.

Files:

  • .changeset/curly-plums-tease.md
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (22)
  • GitHub Check: Integration Tests (billing, chrome)
  • GitHub Check: Integration Tests (custom, chrome)
  • GitHub Check: Integration Tests (nextjs, chrome, 14)
  • GitHub Check: Integration Tests (nextjs, chrome, 15)
  • GitHub Check: Integration Tests (machine, chrome)
  • GitHub Check: Integration Tests (tanstack-react-start, chrome)
  • GitHub Check: Integration Tests (nuxt, chrome)
  • GitHub Check: Integration Tests (vue, chrome)
  • GitHub Check: Integration Tests (expo-web, chrome)
  • GitHub Check: Integration Tests (react-router, chrome)
  • GitHub Check: Integration Tests (astro, chrome)
  • GitHub Check: Integration Tests (localhost, chrome)
  • GitHub Check: Integration Tests (quickstart, chrome)
  • GitHub Check: Integration Tests (ap-flows, chrome)
  • GitHub Check: Integration Tests (sessions, chrome)
  • GitHub Check: Integration Tests (elements, chrome)
  • GitHub Check: Integration Tests (express, chrome)
  • GitHub Check: Integration Tests (generic, chrome)
  • GitHub Check: Static analysis
  • GitHub Check: Unit Tests (22, **)
  • GitHub Check: semgrep-cloud-platform/scan
  • GitHub Check: semgrep-cloud-platform/scan
🔇 Additional comments (1)
.changeset/curly-plums-tease.md (1)

1-6: Changeset looks correct for a peer range expansion (minor bump).

Accurately communicates “Add support for Expo 54” and scopes a minor release for @clerk/expo-passkeys. No issues.

@wobsoriano
wobsoriano merged commit 720ca64 into mainSep 10, 2025
40 checks passed
@wobsoriano
wobsoriano deleted the rob/passkey-expo-54 branch September 10, 2025 22:13
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@wobsoriano@tmilewski@aeliox
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers"); } } catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

chore(expo-passkeys): Add support for Expo 54 - #6752

Merged
wobsoriano merged 3 commits into
mainfrom
rob/passkey-expo-54
Sep 10, 2025
Merged

chore(expo-passkeys): Add support for Expo 54#6752
wobsoriano merged 3 commits into
mainfrom
rob/passkey-expo-54

Conversation

@wobsoriano

@wobsorianowobsoriano commented Sep 10, 2025

Copy link
Copy Markdown
Member

Description

Adjusts the expo peer dep to support Expo 54

https://expo.dev/changelog/sdk-54

Checklist

  • pnpm test runs as expected.
  • pnpm build runs as expected.
  • (If applicable) JSDoc comments have been added or updated for any package exports
  • (If applicable) Documentation has been updated

Type of change

  • 🐛 Bug fix
  • 🌟 New feature
  • 🔨 Breaking change
  • 📖 Refactoring / dependency upgrade / documentation
  • other:

Summary by CodeRabbit

  • New Features

    • Added compatibility with Expo 54, allowing the package to be used in projects targeting the latest Expo 54.x releases.
  • Chores

    • Updated peer dependency range to include Expo 54.x while maintaining exclusion of future major versions.
    • Added release metadata to publish a minor version update.

@vercel

vercelBot commented Sep 10, 2025

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

ProjectDeploymentPreviewCommentsUpdated (UTC)
clerk-js-sandboxReadyReadyPreviewCommentSep 10, 2025 9:21pm

@changeset-bot

changeset-botBot commented Sep 10, 2025

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 7f97749

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages
NameType
@clerk/expo-passkeysMinor
@clerk/clerk-expoPatch

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

@coderabbitai

coderabbitaiBot commented Sep 10, 2025

Copy link
Copy Markdown
Contributor

Walkthrough

Adjusts release metadata and broadens the Expo peer dependency for @clerk/expo-passkeys to include Expo 54.x by updating package.json. No source code or API changes.

Changes

Cohort / File(s)Summary of Changes
Release metadata
\.changeset/curly-plums-tease.md
Adds a changeset declaring a minor version bump for @clerk/expo-passkeys with note “Add support for Expo 54”.
Peer dependency range
packages/expo-passkeys/package.json
Expands expo peer dependency from ">=50 <54" to ">=50 <55" to allow Expo 54.x.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Pre-merge checks (3 passed)

✅ Passed checks (3 passed)
Check nameStatusExplanation
Description Check✅ PassedCheck skipped - CodeRabbit’s high-level summary is enabled.
Title Check✅ PassedThe title “chore(expo-passkeys): Add support for Expo 54” accurately reflects the primary change of updating the peer dependency range to include Expo SDK 54. It is concise, follows conventional commit style, and omits unnecessary detail or file lists. A reviewer scanning the history can immediately understand the purpose of the pull request.
Docstring Coverage✅ PassedNo functions found in the changes. Docstring coverage check skipped.

Poem

I twitch my whiskers, stamp with glee,
A semver hop—so light and free.
From 50 up to 54,
Our Expo path extends once more.
Carrot commits and version cheer,
Springy hops into the new frontier! 🥕🐇

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

  • Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
  • Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
pre_merge_checks:
custom_checks:
- name: "Undocumented Breaking Changes"mode: "warning"instructions: | Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch rob/passkey-expo-54

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

@pkg-pr-new

Copy link
Copy Markdown

Open in StackBlitz

@clerk/agent-toolkit

npm i https://pkg.pr.new/@clerk/agent-toolkit@6752

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@6752

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@6752

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@6752

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@6752

@clerk/dev-cli

npm i https://pkg.pr.new/@clerk/dev-cli@6752

@clerk/elements

npm i https://pkg.pr.new/@clerk/elements@6752

@clerk/clerk-expo

npm i https://pkg.pr.new/@clerk/clerk-expo@6752

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@6752

@clerk/express

npm i https://pkg.pr.new/@clerk/express@6752

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@6752

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@6752

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@6752

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@6752

@clerk/clerk-react

npm i https://pkg.pr.new/@clerk/clerk-react@6752

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@6752

@clerk/remix

npm i https://pkg.pr.new/@clerk/remix@6752

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@6752

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@6752

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@6752

@clerk/themes

npm i https://pkg.pr.new/@clerk/themes@6752

@clerk/types

npm i https://pkg.pr.new/@clerk/types@6752

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@6752

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@6752

commit: 7f97749

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (2)
.changeset/curly-plums-tease.md (1)

5-5: Nit: Make the entry a tad more explicit.

Consider “Add support for Expo SDK 54 (peer: expo >=50 <55)” for clearer release notes.

packages/expo-passkeys/package.json (1)

43-43: Bump devDependencies to Expo SDK 54 for coverage
DevDependencies in packages/expo-passkeys/package.json remain pinned to Expo ~52.0.47—update to ~54.0.0 (or add a CI matrix job for SDK 54) so local/CI tests cover the new range.

- "devDependencies": {- "expo": "~52.0.47"- },+ "devDependencies": {+ "expo": "~54.0.0"+ },
📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 82b84fe and 7f97749.

📒 Files selected for processing (2)
  • .changeset/curly-plums-tease.md (1 hunks)
  • packages/expo-passkeys/package.json (1 hunks)
🧰 Additional context used
📓 Path-based instructions (3)
**/*.{js,jsx,ts,tsx,json,css,scss,md,yaml,yml}

📄 CodeRabbit inference engine (.cursor/rules/development.mdc)

Use Prettier for consistent code formatting

Files:

  • packages/expo-passkeys/package.json
packages/*/package.json

📄 CodeRabbit inference engine (.cursor/rules/global.mdc)

All publishable packages should be placed under the packages/ directory

packages/*/package.json: All publishable packages must be located in the 'packages/' directory.
All packages must be published under the @clerk namespace on npm.
Semantic versioning must be used across all packages.

Files:

  • packages/expo-passkeys/package.json
.changeset/**

📄 CodeRabbit inference engine (.cursor/rules/monorepo.mdc)

Automated releases must use Changesets.

Files:

  • .changeset/curly-plums-tease.md
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (22)
  • GitHub Check: Integration Tests (billing, chrome)
  • GitHub Check: Integration Tests (custom, chrome)
  • GitHub Check: Integration Tests (nextjs, chrome, 14)
  • GitHub Check: Integration Tests (nextjs, chrome, 15)
  • GitHub Check: Integration Tests (machine, chrome)
  • GitHub Check: Integration Tests (tanstack-react-start, chrome)
  • GitHub Check: Integration Tests (nuxt, chrome)
  • GitHub Check: Integration Tests (vue, chrome)
  • GitHub Check: Integration Tests (expo-web, chrome)
  • GitHub Check: Integration Tests (react-router, chrome)
  • GitHub Check: Integration Tests (astro, chrome)
  • GitHub Check: Integration Tests (localhost, chrome)
  • GitHub Check: Integration Tests (quickstart, chrome)
  • GitHub Check: Integration Tests (ap-flows, chrome)
  • GitHub Check: Integration Tests (sessions, chrome)
  • GitHub Check: Integration Tests (elements, chrome)
  • GitHub Check: Integration Tests (express, chrome)
  • GitHub Check: Integration Tests (generic, chrome)
  • GitHub Check: Static analysis
  • GitHub Check: Unit Tests (22, **)
  • GitHub Check: semgrep-cloud-platform/scan
  • GitHub Check: semgrep-cloud-platform/scan
🔇 Additional comments (1)
.changeset/curly-plums-tease.md (1)

1-6: Changeset looks correct for a peer range expansion (minor bump).

Accurately communicates “Add support for Expo 54” and scopes a minor release for @clerk/expo-passkeys. No issues.

@wobsoriano
wobsoriano merged commit 720ca64 into mainSep 10, 2025
40 checks passed
@wobsoriano
wobsoriano deleted the rob/passkey-expo-54 branch September 10, 2025 22:13
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@wobsoriano@tmilewski@aeliox
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode"); } } catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); } })(); })();
Skip to content

chore(expo-passkeys): Add support for Expo 54 - #6752

Merged
wobsoriano merged 3 commits into
mainfrom
rob/passkey-expo-54
Sep 10, 2025
Merged

chore(expo-passkeys): Add support for Expo 54#6752
wobsoriano merged 3 commits into
mainfrom
rob/passkey-expo-54

Conversation

@wobsoriano

@wobsorianowobsoriano commented Sep 10, 2025

Copy link
Copy Markdown
Member

Description

Adjusts the expo peer dep to support Expo 54

https://expo.dev/changelog/sdk-54

Checklist

  • pnpm test runs as expected.
  • pnpm build runs as expected.
  • (If applicable) JSDoc comments have been added or updated for any package exports
  • (If applicable) Documentation has been updated

Type of change

  • 🐛 Bug fix
  • 🌟 New feature
  • 🔨 Breaking change
  • 📖 Refactoring / dependency upgrade / documentation
  • other:

Summary by CodeRabbit

  • New Features

    • Added compatibility with Expo 54, allowing the package to be used in projects targeting the latest Expo 54.x releases.
  • Chores

    • Updated peer dependency range to include Expo 54.x while maintaining exclusion of future major versions.
    • Added release metadata to publish a minor version update.

@vercel

vercelBot commented Sep 10, 2025

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

ProjectDeploymentPreviewCommentsUpdated (UTC)
clerk-js-sandboxReadyReadyPreviewCommentSep 10, 2025 9:21pm

@changeset-bot

changeset-botBot commented Sep 10, 2025

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 7f97749

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages
NameType
@clerk/expo-passkeysMinor
@clerk/clerk-expoPatch

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

@coderabbitai

coderabbitaiBot commented Sep 10, 2025

Copy link
Copy Markdown
Contributor

Walkthrough

Adjusts release metadata and broadens the Expo peer dependency for @clerk/expo-passkeys to include Expo 54.x by updating package.json. No source code or API changes.

Changes

Cohort / File(s)Summary of Changes
Release metadata
\.changeset/curly-plums-tease.md
Adds a changeset declaring a minor version bump for @clerk/expo-passkeys with note “Add support for Expo 54”.
Peer dependency range
packages/expo-passkeys/package.json
Expands expo peer dependency from ">=50 <54" to ">=50 <55" to allow Expo 54.x.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Pre-merge checks (3 passed)

✅ Passed checks (3 passed)
Check nameStatusExplanation
Description Check✅ PassedCheck skipped - CodeRabbit’s high-level summary is enabled.
Title Check✅ PassedThe title “chore(expo-passkeys): Add support for Expo 54” accurately reflects the primary change of updating the peer dependency range to include Expo SDK 54. It is concise, follows conventional commit style, and omits unnecessary detail or file lists. A reviewer scanning the history can immediately understand the purpose of the pull request.
Docstring Coverage✅ PassedNo functions found in the changes. Docstring coverage check skipped.

Poem

I twitch my whiskers, stamp with glee,
A semver hop—so light and free.
From 50 up to 54,
Our Expo path extends once more.
Carrot commits and version cheer,
Springy hops into the new frontier! 🥕🐇

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

  • Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
  • Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
pre_merge_checks:
custom_checks:
- name: "Undocumented Breaking Changes"mode: "warning"instructions: | Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch rob/passkey-expo-54

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

@pkg-pr-new

Copy link
Copy Markdown

Open in StackBlitz

@clerk/agent-toolkit

npm i https://pkg.pr.new/@clerk/agent-toolkit@6752

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@6752

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@6752

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@6752

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@6752

@clerk/dev-cli

npm i https://pkg.pr.new/@clerk/dev-cli@6752

@clerk/elements

npm i https://pkg.pr.new/@clerk/elements@6752

@clerk/clerk-expo

npm i https://pkg.pr.new/@clerk/clerk-expo@6752

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@6752

@clerk/express

npm i https://pkg.pr.new/@clerk/express@6752

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@6752

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@6752

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@6752

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@6752

@clerk/clerk-react

npm i https://pkg.pr.new/@clerk/clerk-react@6752

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@6752

@clerk/remix

npm i https://pkg.pr.new/@clerk/remix@6752

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@6752

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@6752

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@6752

@clerk/themes

npm i https://pkg.pr.new/@clerk/themes@6752

@clerk/types

npm i https://pkg.pr.new/@clerk/types@6752

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@6752

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@6752

commit: 7f97749

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (2)
.changeset/curly-plums-tease.md (1)

5-5: Nit: Make the entry a tad more explicit.

Consider “Add support for Expo SDK 54 (peer: expo >=50 <55)” for clearer release notes.

packages/expo-passkeys/package.json (1)

43-43: Bump devDependencies to Expo SDK 54 for coverage
DevDependencies in packages/expo-passkeys/package.json remain pinned to Expo ~52.0.47—update to ~54.0.0 (or add a CI matrix job for SDK 54) so local/CI tests cover the new range.

- "devDependencies": {- "expo": "~52.0.47"- },+ "devDependencies": {+ "expo": "~54.0.0"+ },
📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 82b84fe and 7f97749.

📒 Files selected for processing (2)
  • .changeset/curly-plums-tease.md (1 hunks)
  • packages/expo-passkeys/package.json (1 hunks)
🧰 Additional context used
📓 Path-based instructions (3)
**/*.{js,jsx,ts,tsx,json,css,scss,md,yaml,yml}

📄 CodeRabbit inference engine (.cursor/rules/development.mdc)

Use Prettier for consistent code formatting

Files:

  • packages/expo-passkeys/package.json
packages/*/package.json

📄 CodeRabbit inference engine (.cursor/rules/global.mdc)

All publishable packages should be placed under the packages/ directory

packages/*/package.json: All publishable packages must be located in the 'packages/' directory.
All packages must be published under the @clerk namespace on npm.
Semantic versioning must be used across all packages.

Files:

  • packages/expo-passkeys/package.json
.changeset/**

📄 CodeRabbit inference engine (.cursor/rules/monorepo.mdc)

Automated releases must use Changesets.

Files:

  • .changeset/curly-plums-tease.md
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (22)
  • GitHub Check: Integration Tests (billing, chrome)
  • GitHub Check: Integration Tests (custom, chrome)
  • GitHub Check: Integration Tests (nextjs, chrome, 14)
  • GitHub Check: Integration Tests (nextjs, chrome, 15)
  • GitHub Check: Integration Tests (machine, chrome)
  • GitHub Check: Integration Tests (tanstack-react-start, chrome)
  • GitHub Check: Integration Tests (nuxt, chrome)
  • GitHub Check: Integration Tests (vue, chrome)
  • GitHub Check: Integration Tests (expo-web, chrome)
  • GitHub Check: Integration Tests (react-router, chrome)
  • GitHub Check: Integration Tests (astro, chrome)
  • GitHub Check: Integration Tests (localhost, chrome)
  • GitHub Check: Integration Tests (quickstart, chrome)
  • GitHub Check: Integration Tests (ap-flows, chrome)
  • GitHub Check: Integration Tests (sessions, chrome)
  • GitHub Check: Integration Tests (elements, chrome)
  • GitHub Check: Integration Tests (express, chrome)
  • GitHub Check: Integration Tests (generic, chrome)
  • GitHub Check: Static analysis
  • GitHub Check: Unit Tests (22, **)
  • GitHub Check: semgrep-cloud-platform/scan
  • GitHub Check: semgrep-cloud-platform/scan
🔇 Additional comments (1)
.changeset/curly-plums-tease.md (1)

1-6: Changeset looks correct for a peer range expansion (minor bump).

Accurately communicates “Add support for Expo 54” and scopes a minor release for @clerk/expo-passkeys. No issues.

@wobsoriano
wobsoriano merged commit 720ca64 into mainSep 10, 2025
40 checks passed
@wobsoriano
wobsoriano deleted the rob/passkey-expo-54 branch September 10, 2025 22:13
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@wobsoriano@tmilewski@aeliox