feat(testing): log response diagnostics when FAPI retries are exhausted by jacekradko · Pull Request #8848 · clerk/javascript

jacekradko · 2026-06-12T17:00:22Z

When the setupClerkTestingToken retry helper exhausts its retries on a 429/5xx, the warning now includes the cf-ray, retry-after, and content-type headers plus the first 500 chars of the response body. A Clerk JSON error body means FAPI's app-level limiter; a Cloudflare error page means an edge rule, and the cf-ray is the direct lookup key for which one. The network-error give-up path now folds the error into the same single warning line.

Motivated by staging E2E run 27401231903, where a 429 storm on attempt_first_factor failed the generic leg and the log gave us no way to tell which side produced the 429s. Diagnostics are gathered best-effort so a failed body read can never prevent the response from being fulfilled.

Summary by CodeRabbit

Bug Fixes
- Enhanced retry exhaustion warnings with HTTP response headers and truncated response body diagnostics.
- Improved network error messages in retry failure warnings.
Tests
- Added comprehensive test coverage for diagnostic logging in retry-exhaustion scenarios.

changeset-bot · 2026-06-12T17:00:26Z

🦋 Changeset detected

Latest commit: 31b8867

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

This PR includes changesets to release 1 package

Name	Type
@clerk/testing	Patch

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

vercel · 2026-06-12T17:00:29Z

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

Project	Deployment	Actions	Updated (UTC)
clerk-js-sandbox	Ready	Preview, Comment	Jun 12, 2026 5:01pm
swingset	Ready	Preview, Comment	Jun 12, 2026 5:01pm

coderabbitai · 2026-06-12T17:00:37Z

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Repository UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: 1dcb9453-38cf-465a-9ecf-4a8bc430c7ae

📥 Commits

Reviewing files that changed from the base of the PR and between 8744728 and 31b8867.

📒 Files selected for processing (3)

.changeset/large-pugs-shake.md
packages/testing/src/playwright/__tests__/setupClerkTestingToken.test.ts
packages/testing/src/playwright/setupClerkTestingToken.ts

📝 Walkthrough

Walkthrough

This PR enhances the setupClerkTestingToken helper's retry failure logging in Playwright tests. When retries are exhausted, warnings now include HTTP response diagnostics (specific headers and truncated body content) for rate-limit attribution, and error messages for network failures. Tests validate the new diagnostics behavior.

Changes

Retry Exhaustion Diagnostics

Layer / File(s)	Summary
Response diagnostics and error logging `packages/testing/src/playwright/setupClerkTestingToken.ts`	When retries on retryable FAPI status codes are exhausted, response diagnostics (`cf-ray`, `retry-after`, `content-type` headers and first 500 characters of body) are gathered and appended to the console warning. Network error exhaustion warnings now also include the error message, not just the URL.
Test coverage for diagnostics `packages/testing/src/playwright/__tests__/setupClerkTestingToken.test.ts`	New tests validate that retry exhaustion warnings include header diagnostics and response body logging, verify truncation of long bodies, and confirm the route fulfills gracefully when diagnostic reads fail. Existing network-error test updated to check for attempt count text and specific error message content.
Changeset documentation `.changeset/large-pugs-shake.md`	Changeset entry documents the `@clerk/testing` patch release with the enhanced diagnostic logging for retry exhaustion warnings.

🎯 2 (Simple) | ⏱️ ~12 minutes

A rabbit hops through failing tests with glee,
Adding headers and hints to the diagnostic spree,
Now when retries grow weary and attempts run out,
The warnings will help us know what it's about! 🐰✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: enhanced logging of response diagnostics when FAPI retries exhaust during 429/5xx failures.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

Create stacked PR
Commit on current branch

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

pkg-pr-new · 2026-06-12T17:03:39Z

Open in StackBlitz

@clerk/astro

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

@clerk/backend

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

@clerk/chrome-extension

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

@clerk/clerk-js

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

@clerk/expo

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

@clerk/expo-passkeys

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

@clerk/express

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

@clerk/fastify

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

@clerk/hono

npm i https://pkg.pr.new/@clerk/hono@8848

@clerk/localizations

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

@clerk/nextjs

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

@clerk/nuxt

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

@clerk/react

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

@clerk/react-router

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

@clerk/shared

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

@clerk/tanstack-react-start

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

@clerk/testing

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

@clerk/ui

npm i https://pkg.pr.new/@clerk/ui@8848

@clerk/upgrade

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

@clerk/vue

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

commit: 31b8867

github-actions · 2026-06-12T17:03:53Z

API Changes Report

Generated by Break Check on 2026-06-12T17:03:51.098Z

Summary

Metric	Count
Packages analyzed	19
Packages with changes	0
🔴 Breaking changes	0
🟡 Non-breaking changes	0
🟢 Additions	0

Note
Break Check could not snapshot 1 subpath; the diff below excludes them.
@clerk/astro ./env: ambient declaration file (no top-level import or export): API Extractor can only analyze module entry points, so this global-augmentation surface cannot be snapshotted; add the subpath to ignoreSubpaths to acknowledge it (API Extractor: Unable to determine module for: /home/runner/_work/javascript/javascript/packages/astro/env.d.ts)

No API Changes Detected

All packages have stable APIs with no detected changes.

Report generated by Break Check

_{Last ran on 31b8867.}

jacekradko · 2026-06-12T17:00:22Z

When the setupClerkTestingToken retry helper exhausts its retries on a 429/5xx, the warning now includes the cf-ray, retry-after, and content-type headers plus the first 500 chars of the response body. A Clerk JSON error body means FAPI's app-level limiter; a Cloudflare error page means an edge rule, and the cf-ray is the direct lookup key for which one. The network-error give-up path now folds the error into the same single warning line.

Motivated by staging E2E run 27401231903, where a 429 storm on attempt_first_factor failed the generic leg and the log gave us no way to tell which side produced the 429s. Diagnostics are gathered best-effort so a failed body read can never prevent the response from being fulfilled.

Summary by CodeRabbit

Bug Fixes
- Enhanced retry exhaustion warnings with HTTP response headers and truncated response body diagnostics.
- Improved network error messages in retry failure warnings.
Tests
- Added comprehensive test coverage for diagnostic logging in retry-exhaustion scenarios.

changeset-bot · 2026-06-12T17:00:26Z

🦋 Changeset detected

Latest commit: 31b8867

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

This PR includes changesets to release 1 package

Name	Type
@clerk/testing	Patch

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

vercel · 2026-06-12T17:00:29Z

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

Project	Deployment	Actions	Updated (UTC)
clerk-js-sandbox	Ready	Preview, Comment	Jun 12, 2026 5:01pm
swingset	Ready	Preview, Comment	Jun 12, 2026 5:01pm

coderabbitai · 2026-06-12T17:00:37Z

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Repository UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: 1dcb9453-38cf-465a-9ecf-4a8bc430c7ae

📥 Commits

Reviewing files that changed from the base of the PR and between 8744728 and 31b8867.

📒 Files selected for processing (3)

.changeset/large-pugs-shake.md
packages/testing/src/playwright/__tests__/setupClerkTestingToken.test.ts
packages/testing/src/playwright/setupClerkTestingToken.ts

📝 Walkthrough

Walkthrough

This PR enhances the setupClerkTestingToken helper's retry failure logging in Playwright tests. When retries are exhausted, warnings now include HTTP response diagnostics (specific headers and truncated body content) for rate-limit attribution, and error messages for network failures. Tests validate the new diagnostics behavior.

Changes

Retry Exhaustion Diagnostics

Layer / File(s)	Summary
Response diagnostics and error logging `packages/testing/src/playwright/setupClerkTestingToken.ts`	When retries on retryable FAPI status codes are exhausted, response diagnostics (`cf-ray`, `retry-after`, `content-type` headers and first 500 characters of body) are gathered and appended to the console warning. Network error exhaustion warnings now also include the error message, not just the URL.
Test coverage for diagnostics `packages/testing/src/playwright/__tests__/setupClerkTestingToken.test.ts`	New tests validate that retry exhaustion warnings include header diagnostics and response body logging, verify truncation of long bodies, and confirm the route fulfills gracefully when diagnostic reads fail. Existing network-error test updated to check for attempt count text and specific error message content.
Changeset documentation `.changeset/large-pugs-shake.md`	Changeset entry documents the `@clerk/testing` patch release with the enhanced diagnostic logging for retry exhaustion warnings.

🎯 2 (Simple) | ⏱️ ~12 minutes

A rabbit hops through failing tests with glee,
Adding headers and hints to the diagnostic spree,
Now when retries grow weary and attempts run out,
The warnings will help us know what it's about! 🐰✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: enhanced logging of response diagnostics when FAPI retries exhaust during 429/5xx failures.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

Create stacked PR
Commit on current branch

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

pkg-pr-new · 2026-06-12T17:03:39Z

Open in StackBlitz

@clerk/astro

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

@clerk/backend

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

@clerk/chrome-extension

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

@clerk/clerk-js

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

@clerk/expo

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

@clerk/expo-passkeys

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

@clerk/express

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

@clerk/fastify

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

@clerk/hono

npm i https://pkg.pr.new/@clerk/hono@8848

@clerk/localizations

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

@clerk/nextjs

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

@clerk/nuxt

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

@clerk/react

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

@clerk/react-router

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

@clerk/shared

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

@clerk/tanstack-react-start

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

@clerk/testing

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

@clerk/ui

npm i https://pkg.pr.new/@clerk/ui@8848

@clerk/upgrade

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

@clerk/vue

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

commit: 31b8867

github-actions · 2026-06-12T17:03:53Z

API Changes Report

Generated by Break Check on 2026-06-12T17:03:51.098Z

Summary

Metric	Count
Packages analyzed	19
Packages with changes	0
🔴 Breaking changes	0
🟡 Non-breaking changes	0
🟢 Additions	0

Note
Break Check could not snapshot 1 subpath; the diff below excludes them.
@clerk/astro ./env: ambient declaration file (no top-level import or export): API Extractor can only analyze module entry points, so this global-augmentation surface cannot be snapshotted; add the subpath to ignoreSubpaths to acknowledge it (API Extractor: Unable to determine module for: /home/runner/_work/javascript/javascript/packages/astro/env.d.ts)

No API Changes Detected

All packages have stable APIs with no detected changes.

Report generated by Break Check

_{Last ran on 31b8867.}

jacekradko · 2026-06-12T17:00:22Z

When the setupClerkTestingToken retry helper exhausts its retries on a 429/5xx, the warning now includes the cf-ray, retry-after, and content-type headers plus the first 500 chars of the response body. A Clerk JSON error body means FAPI's app-level limiter; a Cloudflare error page means an edge rule, and the cf-ray is the direct lookup key for which one. The network-error give-up path now folds the error into the same single warning line.

Motivated by staging E2E run 27401231903, where a 429 storm on attempt_first_factor failed the generic leg and the log gave us no way to tell which side produced the 429s. Diagnostics are gathered best-effort so a failed body read can never prevent the response from being fulfilled.

Summary by CodeRabbit

Bug Fixes
- Enhanced retry exhaustion warnings with HTTP response headers and truncated response body diagnostics.
- Improved network error messages in retry failure warnings.
Tests
- Added comprehensive test coverage for diagnostic logging in retry-exhaustion scenarios.

changeset-bot · 2026-06-12T17:00:26Z

🦋 Changeset detected

Latest commit: 31b8867

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

This PR includes changesets to release 1 package

Name	Type
@clerk/testing	Patch

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

vercel · 2026-06-12T17:00:29Z

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

Project	Deployment	Actions	Updated (UTC)
clerk-js-sandbox	Ready	Preview, Comment	Jun 12, 2026 5:01pm
swingset	Ready	Preview, Comment	Jun 12, 2026 5:01pm

coderabbitai · 2026-06-12T17:00:37Z

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Repository UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: 1dcb9453-38cf-465a-9ecf-4a8bc430c7ae

📥 Commits

Reviewing files that changed from the base of the PR and between 8744728 and 31b8867.

📒 Files selected for processing (3)

.changeset/large-pugs-shake.md
packages/testing/src/playwright/__tests__/setupClerkTestingToken.test.ts
packages/testing/src/playwright/setupClerkTestingToken.ts

📝 Walkthrough

Walkthrough

This PR enhances the setupClerkTestingToken helper's retry failure logging in Playwright tests. When retries are exhausted, warnings now include HTTP response diagnostics (specific headers and truncated body content) for rate-limit attribution, and error messages for network failures. Tests validate the new diagnostics behavior.

Changes

Retry Exhaustion Diagnostics

Layer / File(s)	Summary
Response diagnostics and error logging `packages/testing/src/playwright/setupClerkTestingToken.ts`	When retries on retryable FAPI status codes are exhausted, response diagnostics (`cf-ray`, `retry-after`, `content-type` headers and first 500 characters of body) are gathered and appended to the console warning. Network error exhaustion warnings now also include the error message, not just the URL.
Test coverage for diagnostics `packages/testing/src/playwright/__tests__/setupClerkTestingToken.test.ts`	New tests validate that retry exhaustion warnings include header diagnostics and response body logging, verify truncation of long bodies, and confirm the route fulfills gracefully when diagnostic reads fail. Existing network-error test updated to check for attempt count text and specific error message content.
Changeset documentation `.changeset/large-pugs-shake.md`	Changeset entry documents the `@clerk/testing` patch release with the enhanced diagnostic logging for retry exhaustion warnings.

🎯 2 (Simple) | ⏱️ ~12 minutes

A rabbit hops through failing tests with glee,
Adding headers and hints to the diagnostic spree,
Now when retries grow weary and attempts run out,
The warnings will help us know what it's about! 🐰✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: enhanced logging of response diagnostics when FAPI retries exhaust during 429/5xx failures.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

Create stacked PR
Commit on current branch

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

pkg-pr-new · 2026-06-12T17:03:39Z

Open in StackBlitz

@clerk/astro

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

@clerk/backend

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

@clerk/chrome-extension

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

@clerk/clerk-js

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

@clerk/expo

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

@clerk/expo-passkeys

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

@clerk/express

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

@clerk/fastify

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

@clerk/hono

npm i https://pkg.pr.new/@clerk/hono@8848

@clerk/localizations

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

@clerk/nextjs

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

@clerk/nuxt

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

@clerk/react

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

@clerk/react-router

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

@clerk/shared

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

@clerk/tanstack-react-start

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

@clerk/testing

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

@clerk/ui

npm i https://pkg.pr.new/@clerk/ui@8848

@clerk/upgrade

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

@clerk/vue

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

commit: 31b8867

github-actions · 2026-06-12T17:03:53Z

API Changes Report

Generated by Break Check on 2026-06-12T17:03:51.098Z

Summary

Metric	Count
Packages analyzed	19
Packages with changes	0
🔴 Breaking changes	0
🟡 Non-breaking changes	0
🟢 Additions	0

Note
Break Check could not snapshot 1 subpath; the diff below excludes them.
@clerk/astro ./env: ambient declaration file (no top-level import or export): API Extractor can only analyze module entry points, so this global-augmentation surface cannot be snapshotted; add the subpath to ignoreSubpaths to acknowledge it (API Extractor: Unable to determine module for: /home/runner/_work/javascript/javascript/packages/astro/env.d.ts)

No API Changes Detected

All packages have stable APIs with no detected changes.

Report generated by Break Check

_{Last ran on 31b8867.}

jacekradko · 2026-06-12T17:00:22Z

When the setupClerkTestingToken retry helper exhausts its retries on a 429/5xx, the warning now includes the cf-ray, retry-after, and content-type headers plus the first 500 chars of the response body. A Clerk JSON error body means FAPI's app-level limiter; a Cloudflare error page means an edge rule, and the cf-ray is the direct lookup key for which one. The network-error give-up path now folds the error into the same single warning line.

Motivated by staging E2E run 27401231903, where a 429 storm on attempt_first_factor failed the generic leg and the log gave us no way to tell which side produced the 429s. Diagnostics are gathered best-effort so a failed body read can never prevent the response from being fulfilled.

Summary by CodeRabbit

Bug Fixes
- Enhanced retry exhaustion warnings with HTTP response headers and truncated response body diagnostics.
- Improved network error messages in retry failure warnings.
Tests
- Added comprehensive test coverage for diagnostic logging in retry-exhaustion scenarios.

changeset-bot · 2026-06-12T17:00:26Z

🦋 Changeset detected

Latest commit: 31b8867

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

This PR includes changesets to release 1 package

Name	Type
@clerk/testing	Patch

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

vercel · 2026-06-12T17:00:29Z

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

Project	Deployment	Actions	Updated (UTC)
clerk-js-sandbox	Ready	Preview, Comment	Jun 12, 2026 5:01pm
swingset	Ready	Preview, Comment	Jun 12, 2026 5:01pm

coderabbitai · 2026-06-12T17:00:37Z

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Repository UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: 1dcb9453-38cf-465a-9ecf-4a8bc430c7ae

📥 Commits

Reviewing files that changed from the base of the PR and between 8744728 and 31b8867.

📒 Files selected for processing (3)

.changeset/large-pugs-shake.md
packages/testing/src/playwright/__tests__/setupClerkTestingToken.test.ts
packages/testing/src/playwright/setupClerkTestingToken.ts

📝 Walkthrough

Walkthrough

This PR enhances the setupClerkTestingToken helper's retry failure logging in Playwright tests. When retries are exhausted, warnings now include HTTP response diagnostics (specific headers and truncated body content) for rate-limit attribution, and error messages for network failures. Tests validate the new diagnostics behavior.

Changes

Retry Exhaustion Diagnostics

Layer / File(s)	Summary
Response diagnostics and error logging `packages/testing/src/playwright/setupClerkTestingToken.ts`	When retries on retryable FAPI status codes are exhausted, response diagnostics (`cf-ray`, `retry-after`, `content-type` headers and first 500 characters of body) are gathered and appended to the console warning. Network error exhaustion warnings now also include the error message, not just the URL.
Test coverage for diagnostics `packages/testing/src/playwright/__tests__/setupClerkTestingToken.test.ts`	New tests validate that retry exhaustion warnings include header diagnostics and response body logging, verify truncation of long bodies, and confirm the route fulfills gracefully when diagnostic reads fail. Existing network-error test updated to check for attempt count text and specific error message content.
Changeset documentation `.changeset/large-pugs-shake.md`	Changeset entry documents the `@clerk/testing` patch release with the enhanced diagnostic logging for retry exhaustion warnings.

🎯 2 (Simple) | ⏱️ ~12 minutes

A rabbit hops through failing tests with glee,
Adding headers and hints to the diagnostic spree,
Now when retries grow weary and attempts run out,
The warnings will help us know what it's about! 🐰✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: enhanced logging of response diagnostics when FAPI retries exhaust during 429/5xx failures.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

Create stacked PR
Commit on current branch

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

pkg-pr-new · 2026-06-12T17:03:39Z

Open in StackBlitz

@clerk/astro

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

@clerk/backend

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

@clerk/chrome-extension

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

@clerk/clerk-js

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

@clerk/expo

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

@clerk/expo-passkeys

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

@clerk/express

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

@clerk/fastify

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

@clerk/hono

npm i https://pkg.pr.new/@clerk/hono@8848

@clerk/localizations

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

@clerk/nextjs

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

@clerk/nuxt

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

@clerk/react

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

@clerk/react-router

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

@clerk/shared

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

@clerk/tanstack-react-start

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

@clerk/testing

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

@clerk/ui

npm i https://pkg.pr.new/@clerk/ui@8848

@clerk/upgrade

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

@clerk/vue

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

commit: 31b8867

github-actions · 2026-06-12T17:03:53Z

API Changes Report

Generated by Break Check on 2026-06-12T17:03:51.098Z

Summary

Metric	Count
Packages analyzed	19
Packages with changes	0
🔴 Breaking changes	0
🟡 Non-breaking changes	0
🟢 Additions	0

Note
Break Check could not snapshot 1 subpath; the diff below excludes them.
@clerk/astro ./env: ambient declaration file (no top-level import or export): API Extractor can only analyze module entry points, so this global-augmentation surface cannot be snapshotted; add the subpath to ignoreSubpaths to acknowledge it (API Extractor: Unable to determine module for: /home/runner/_work/javascript/javascript/packages/astro/env.d.ts)

No API Changes Detected

All packages have stable APIs with no detected changes.

Report generated by Break Check

_{Last ran on 31b8867.}

jacekradko · 2026-06-12T17:00:22Z

When the setupClerkTestingToken retry helper exhausts its retries on a 429/5xx, the warning now includes the cf-ray, retry-after, and content-type headers plus the first 500 chars of the response body. A Clerk JSON error body means FAPI's app-level limiter; a Cloudflare error page means an edge rule, and the cf-ray is the direct lookup key for which one. The network-error give-up path now folds the error into the same single warning line.

Motivated by staging E2E run 27401231903, where a 429 storm on attempt_first_factor failed the generic leg and the log gave us no way to tell which side produced the 429s. Diagnostics are gathered best-effort so a failed body read can never prevent the response from being fulfilled.

Summary by CodeRabbit

Bug Fixes
- Enhanced retry exhaustion warnings with HTTP response headers and truncated response body diagnostics.
- Improved network error messages in retry failure warnings.
Tests
- Added comprehensive test coverage for diagnostic logging in retry-exhaustion scenarios.

changeset-bot · 2026-06-12T17:00:26Z

🦋 Changeset detected

Latest commit: 31b8867

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

This PR includes changesets to release 1 package

Name	Type
@clerk/testing	Patch

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

vercel · 2026-06-12T17:00:29Z

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

Project	Deployment	Actions	Updated (UTC)
clerk-js-sandbox	Ready	Preview, Comment	Jun 12, 2026 5:01pm
swingset	Ready	Preview, Comment	Jun 12, 2026 5:01pm

coderabbitai · 2026-06-12T17:00:37Z

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Repository UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: 1dcb9453-38cf-465a-9ecf-4a8bc430c7ae

📥 Commits

Reviewing files that changed from the base of the PR and between 8744728 and 31b8867.

📒 Files selected for processing (3)

.changeset/large-pugs-shake.md
packages/testing/src/playwright/__tests__/setupClerkTestingToken.test.ts
packages/testing/src/playwright/setupClerkTestingToken.ts

📝 Walkthrough

Walkthrough

This PR enhances the setupClerkTestingToken helper's retry failure logging in Playwright tests. When retries are exhausted, warnings now include HTTP response diagnostics (specific headers and truncated body content) for rate-limit attribution, and error messages for network failures. Tests validate the new diagnostics behavior.

Changes

Retry Exhaustion Diagnostics

Layer / File(s)	Summary
Response diagnostics and error logging `packages/testing/src/playwright/setupClerkTestingToken.ts`	When retries on retryable FAPI status codes are exhausted, response diagnostics (`cf-ray`, `retry-after`, `content-type` headers and first 500 characters of body) are gathered and appended to the console warning. Network error exhaustion warnings now also include the error message, not just the URL.
Test coverage for diagnostics `packages/testing/src/playwright/__tests__/setupClerkTestingToken.test.ts`	New tests validate that retry exhaustion warnings include header diagnostics and response body logging, verify truncation of long bodies, and confirm the route fulfills gracefully when diagnostic reads fail. Existing network-error test updated to check for attempt count text and specific error message content.
Changeset documentation `.changeset/large-pugs-shake.md`	Changeset entry documents the `@clerk/testing` patch release with the enhanced diagnostic logging for retry exhaustion warnings.

🎯 2 (Simple) | ⏱️ ~12 minutes

A rabbit hops through failing tests with glee,
Adding headers and hints to the diagnostic spree,
Now when retries grow weary and attempts run out,
The warnings will help us know what it's about! 🐰✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: enhanced logging of response diagnostics when FAPI retries exhaust during 429/5xx failures.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

Create stacked PR
Commit on current branch

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

pkg-pr-new · 2026-06-12T17:03:39Z

Open in StackBlitz

@clerk/astro

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

@clerk/backend

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

@clerk/chrome-extension

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

@clerk/clerk-js

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

@clerk/expo

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

@clerk/expo-passkeys

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

@clerk/express

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

@clerk/fastify

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

@clerk/hono

npm i https://pkg.pr.new/@clerk/hono@8848

@clerk/localizations

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

@clerk/nextjs

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

@clerk/nuxt

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

@clerk/react

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

@clerk/react-router

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

@clerk/shared

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

@clerk/tanstack-react-start

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

@clerk/testing

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

@clerk/ui

npm i https://pkg.pr.new/@clerk/ui@8848

@clerk/upgrade

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

@clerk/vue

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

commit: 31b8867

github-actions · 2026-06-12T17:03:53Z

API Changes Report

Generated by Break Check on 2026-06-12T17:03:51.098Z

Summary

Metric	Count
Packages analyzed	19
Packages with changes	0
🔴 Breaking changes	0
🟡 Non-breaking changes	0
🟢 Additions	0

Note
Break Check could not snapshot 1 subpath; the diff below excludes them.
@clerk/astro ./env: ambient declaration file (no top-level import or export): API Extractor can only analyze module entry points, so this global-augmentation surface cannot be snapshotted; add the subpath to ignoreSubpaths to acknowledge it (API Extractor: Unable to determine module for: /home/runner/_work/javascript/javascript/packages/astro/env.d.ts)

No API Changes Detected

All packages have stable APIs with no detected changes.

Report generated by Break Check

_{Last ran on 31b8867.}

jacekradko · 2026-06-12T17:00:22Z

When the setupClerkTestingToken retry helper exhausts its retries on a 429/5xx, the warning now includes the cf-ray, retry-after, and content-type headers plus the first 500 chars of the response body. A Clerk JSON error body means FAPI's app-level limiter; a Cloudflare error page means an edge rule, and the cf-ray is the direct lookup key for which one. The network-error give-up path now folds the error into the same single warning line.

Motivated by staging E2E run 27401231903, where a 429 storm on attempt_first_factor failed the generic leg and the log gave us no way to tell which side produced the 429s. Diagnostics are gathered best-effort so a failed body read can never prevent the response from being fulfilled.

Summary by CodeRabbit

Bug Fixes
- Enhanced retry exhaustion warnings with HTTP response headers and truncated response body diagnostics.
- Improved network error messages in retry failure warnings.
Tests
- Added comprehensive test coverage for diagnostic logging in retry-exhaustion scenarios.

changeset-bot · 2026-06-12T17:00:26Z

🦋 Changeset detected

Latest commit: 31b8867

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

This PR includes changesets to release 1 package

Name	Type
@clerk/testing	Patch

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

vercel · 2026-06-12T17:00:29Z

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

Project	Deployment	Actions	Updated (UTC)
clerk-js-sandbox	Ready	Preview, Comment	Jun 12, 2026 5:01pm
swingset	Ready	Preview, Comment	Jun 12, 2026 5:01pm

coderabbitai · 2026-06-12T17:00:37Z

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Repository UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: 1dcb9453-38cf-465a-9ecf-4a8bc430c7ae

📥 Commits

Reviewing files that changed from the base of the PR and between 8744728 and 31b8867.

📒 Files selected for processing (3)

.changeset/large-pugs-shake.md
packages/testing/src/playwright/__tests__/setupClerkTestingToken.test.ts
packages/testing/src/playwright/setupClerkTestingToken.ts

📝 Walkthrough

Walkthrough

This PR enhances the setupClerkTestingToken helper's retry failure logging in Playwright tests. When retries are exhausted, warnings now include HTTP response diagnostics (specific headers and truncated body content) for rate-limit attribution, and error messages for network failures. Tests validate the new diagnostics behavior.

Changes

Retry Exhaustion Diagnostics

Layer / File(s)	Summary
Response diagnostics and error logging `packages/testing/src/playwright/setupClerkTestingToken.ts`	When retries on retryable FAPI status codes are exhausted, response diagnostics (`cf-ray`, `retry-after`, `content-type` headers and first 500 characters of body) are gathered and appended to the console warning. Network error exhaustion warnings now also include the error message, not just the URL.
Test coverage for diagnostics `packages/testing/src/playwright/__tests__/setupClerkTestingToken.test.ts`	New tests validate that retry exhaustion warnings include header diagnostics and response body logging, verify truncation of long bodies, and confirm the route fulfills gracefully when diagnostic reads fail. Existing network-error test updated to check for attempt count text and specific error message content.
Changeset documentation `.changeset/large-pugs-shake.md`	Changeset entry documents the `@clerk/testing` patch release with the enhanced diagnostic logging for retry exhaustion warnings.

🎯 2 (Simple) | ⏱️ ~12 minutes

A rabbit hops through failing tests with glee,
Adding headers and hints to the diagnostic spree,
Now when retries grow weary and attempts run out,
The warnings will help us know what it's about! 🐰✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: enhanced logging of response diagnostics when FAPI retries exhaust during 429/5xx failures.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

Create stacked PR
Commit on current branch

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

pkg-pr-new · 2026-06-12T17:03:39Z

Open in StackBlitz

@clerk/astro

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

@clerk/backend

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

@clerk/chrome-extension

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

@clerk/clerk-js

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

@clerk/expo

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

@clerk/expo-passkeys

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

@clerk/express

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

@clerk/fastify

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

@clerk/hono

npm i https://pkg.pr.new/@clerk/hono@8848

@clerk/localizations

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

@clerk/nextjs

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

@clerk/nuxt

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

@clerk/react

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

@clerk/react-router

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

@clerk/shared

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

@clerk/tanstack-react-start

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

@clerk/testing

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

@clerk/ui

npm i https://pkg.pr.new/@clerk/ui@8848

@clerk/upgrade

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

@clerk/vue

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

commit: 31b8867

github-actions · 2026-06-12T17:03:53Z

API Changes Report

Generated by Break Check on 2026-06-12T17:03:51.098Z

Summary

Metric	Count
Packages analyzed	19
Packages with changes	0
🔴 Breaking changes	0
🟡 Non-breaking changes	0
🟢 Additions	0

Note
Break Check could not snapshot 1 subpath; the diff below excludes them.
@clerk/astro ./env: ambient declaration file (no top-level import or export): API Extractor can only analyze module entry points, so this global-augmentation surface cannot be snapshotted; add the subpath to ignoreSubpaths to acknowledge it (API Extractor: Unable to determine module for: /home/runner/_work/javascript/javascript/packages/astro/env.d.ts)

No API Changes Detected

All packages have stable APIs with no detected changes.

Report generated by Break Check

_{Last ran on 31b8867.}

jacekradko · 2026-06-12T17:00:22Z

When the setupClerkTestingToken retry helper exhausts its retries on a 429/5xx, the warning now includes the cf-ray, retry-after, and content-type headers plus the first 500 chars of the response body. A Clerk JSON error body means FAPI's app-level limiter; a Cloudflare error page means an edge rule, and the cf-ray is the direct lookup key for which one. The network-error give-up path now folds the error into the same single warning line.

Motivated by staging E2E run 27401231903, where a 429 storm on attempt_first_factor failed the generic leg and the log gave us no way to tell which side produced the 429s. Diagnostics are gathered best-effort so a failed body read can never prevent the response from being fulfilled.

Summary by CodeRabbit

Bug Fixes
- Enhanced retry exhaustion warnings with HTTP response headers and truncated response body diagnostics.
- Improved network error messages in retry failure warnings.
Tests
- Added comprehensive test coverage for diagnostic logging in retry-exhaustion scenarios.

changeset-bot · 2026-06-12T17:00:26Z

🦋 Changeset detected

Latest commit: 31b8867

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

This PR includes changesets to release 1 package

Name	Type
@clerk/testing	Patch

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

vercel · 2026-06-12T17:00:29Z

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

Project	Deployment	Actions	Updated (UTC)
clerk-js-sandbox	Ready	Preview, Comment	Jun 12, 2026 5:01pm
swingset	Ready	Preview, Comment	Jun 12, 2026 5:01pm

coderabbitai · 2026-06-12T17:00:37Z

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Repository UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: 1dcb9453-38cf-465a-9ecf-4a8bc430c7ae

📥 Commits

Reviewing files that changed from the base of the PR and between 8744728 and 31b8867.

📒 Files selected for processing (3)

.changeset/large-pugs-shake.md
packages/testing/src/playwright/__tests__/setupClerkTestingToken.test.ts
packages/testing/src/playwright/setupClerkTestingToken.ts

📝 Walkthrough

Walkthrough

This PR enhances the setupClerkTestingToken helper's retry failure logging in Playwright tests. When retries are exhausted, warnings now include HTTP response diagnostics (specific headers and truncated body content) for rate-limit attribution, and error messages for network failures. Tests validate the new diagnostics behavior.

Changes

Retry Exhaustion Diagnostics

Layer / File(s)	Summary
Response diagnostics and error logging `packages/testing/src/playwright/setupClerkTestingToken.ts`	When retries on retryable FAPI status codes are exhausted, response diagnostics (`cf-ray`, `retry-after`, `content-type` headers and first 500 characters of body) are gathered and appended to the console warning. Network error exhaustion warnings now also include the error message, not just the URL.
Test coverage for diagnostics `packages/testing/src/playwright/__tests__/setupClerkTestingToken.test.ts`	New tests validate that retry exhaustion warnings include header diagnostics and response body logging, verify truncation of long bodies, and confirm the route fulfills gracefully when diagnostic reads fail. Existing network-error test updated to check for attempt count text and specific error message content.
Changeset documentation `.changeset/large-pugs-shake.md`	Changeset entry documents the `@clerk/testing` patch release with the enhanced diagnostic logging for retry exhaustion warnings.

🎯 2 (Simple) | ⏱️ ~12 minutes

A rabbit hops through failing tests with glee,
Adding headers and hints to the diagnostic spree,
Now when retries grow weary and attempts run out,
The warnings will help us know what it's about! 🐰✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: enhanced logging of response diagnostics when FAPI retries exhaust during 429/5xx failures.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

Create stacked PR
Commit on current branch

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

pkg-pr-new · 2026-06-12T17:03:39Z

Open in StackBlitz

@clerk/astro

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

@clerk/backend

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

@clerk/chrome-extension

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

@clerk/clerk-js

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

@clerk/expo

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

@clerk/expo-passkeys

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

@clerk/express

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

@clerk/fastify

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

@clerk/hono

npm i https://pkg.pr.new/@clerk/hono@8848

@clerk/localizations

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

@clerk/nextjs

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

@clerk/nuxt

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

@clerk/react

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

@clerk/react-router

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

@clerk/shared

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

@clerk/tanstack-react-start

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

@clerk/testing

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

@clerk/ui

npm i https://pkg.pr.new/@clerk/ui@8848

@clerk/upgrade

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

@clerk/vue

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

commit: 31b8867

github-actions · 2026-06-12T17:03:53Z

API Changes Report

Generated by Break Check on 2026-06-12T17:03:51.098Z

Summary

Metric	Count
Packages analyzed	19
Packages with changes	0
🔴 Breaking changes	0
🟡 Non-breaking changes	0
🟢 Additions	0

Note
Break Check could not snapshot 1 subpath; the diff below excludes them.
@clerk/astro ./env: ambient declaration file (no top-level import or export): API Extractor can only analyze module entry points, so this global-augmentation surface cannot be snapshotted; add the subpath to ignoreSubpaths to acknowledge it (API Extractor: Unable to determine module for: /home/runner/_work/javascript/javascript/packages/astro/env.d.ts)

No API Changes Detected

All packages have stable APIs with no detected changes.

Report generated by Break Check

_{Last ran on 31b8867.}

jacekradko · 2026-06-12T17:00:22Z

When the setupClerkTestingToken retry helper exhausts its retries on a 429/5xx, the warning now includes the cf-ray, retry-after, and content-type headers plus the first 500 chars of the response body. A Clerk JSON error body means FAPI's app-level limiter; a Cloudflare error page means an edge rule, and the cf-ray is the direct lookup key for which one. The network-error give-up path now folds the error into the same single warning line.

Motivated by staging E2E run 27401231903, where a 429 storm on attempt_first_factor failed the generic leg and the log gave us no way to tell which side produced the 429s. Diagnostics are gathered best-effort so a failed body read can never prevent the response from being fulfilled.

Summary by CodeRabbit

Bug Fixes
- Enhanced retry exhaustion warnings with HTTP response headers and truncated response body diagnostics.
- Improved network error messages in retry failure warnings.
Tests
- Added comprehensive test coverage for diagnostic logging in retry-exhaustion scenarios.

changeset-bot · 2026-06-12T17:00:26Z

🦋 Changeset detected

Latest commit: 31b8867

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

This PR includes changesets to release 1 package

Name	Type
@clerk/testing	Patch

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

vercel · 2026-06-12T17:00:29Z

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

Project	Deployment	Actions	Updated (UTC)
clerk-js-sandbox	Ready	Preview, Comment	Jun 12, 2026 5:01pm
swingset	Ready	Preview, Comment	Jun 12, 2026 5:01pm

coderabbitai · 2026-06-12T17:00:37Z

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Repository UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: 1dcb9453-38cf-465a-9ecf-4a8bc430c7ae

📥 Commits

Reviewing files that changed from the base of the PR and between 8744728 and 31b8867.

📒 Files selected for processing (3)

.changeset/large-pugs-shake.md
packages/testing/src/playwright/__tests__/setupClerkTestingToken.test.ts
packages/testing/src/playwright/setupClerkTestingToken.ts

📝 Walkthrough

Walkthrough

This PR enhances the setupClerkTestingToken helper's retry failure logging in Playwright tests. When retries are exhausted, warnings now include HTTP response diagnostics (specific headers and truncated body content) for rate-limit attribution, and error messages for network failures. Tests validate the new diagnostics behavior.

Changes

Retry Exhaustion Diagnostics

Layer / File(s)	Summary
Response diagnostics and error logging `packages/testing/src/playwright/setupClerkTestingToken.ts`	When retries on retryable FAPI status codes are exhausted, response diagnostics (`cf-ray`, `retry-after`, `content-type` headers and first 500 characters of body) are gathered and appended to the console warning. Network error exhaustion warnings now also include the error message, not just the URL.
Test coverage for diagnostics `packages/testing/src/playwright/__tests__/setupClerkTestingToken.test.ts`	New tests validate that retry exhaustion warnings include header diagnostics and response body logging, verify truncation of long bodies, and confirm the route fulfills gracefully when diagnostic reads fail. Existing network-error test updated to check for attempt count text and specific error message content.
Changeset documentation `.changeset/large-pugs-shake.md`	Changeset entry documents the `@clerk/testing` patch release with the enhanced diagnostic logging for retry exhaustion warnings.

🎯 2 (Simple) | ⏱️ ~12 minutes

A rabbit hops through failing tests with glee,
Adding headers and hints to the diagnostic spree,
Now when retries grow weary and attempts run out,
The warnings will help us know what it's about! 🐰✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: enhanced logging of response diagnostics when FAPI retries exhaust during 429/5xx failures.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

Create stacked PR
Commit on current branch

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

pkg-pr-new · 2026-06-12T17:03:39Z

Open in StackBlitz

@clerk/astro

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

@clerk/backend

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

@clerk/chrome-extension

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

@clerk/clerk-js

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

@clerk/expo

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

@clerk/expo-passkeys

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

@clerk/express

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

@clerk/fastify

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

@clerk/hono

npm i https://pkg.pr.new/@clerk/hono@8848

@clerk/localizations

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

@clerk/nextjs

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

@clerk/nuxt

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

@clerk/react

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

@clerk/react-router

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

@clerk/shared

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

@clerk/tanstack-react-start

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

@clerk/testing

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

@clerk/ui

npm i https://pkg.pr.new/@clerk/ui@8848

@clerk/upgrade

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

@clerk/vue

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

commit: 31b8867

github-actions · 2026-06-12T17:03:53Z

API Changes Report

Generated by Break Check on 2026-06-12T17:03:51.098Z

Summary

Metric	Count
Packages analyzed	19
Packages with changes	0
🔴 Breaking changes	0
🟡 Non-breaking changes	0
🟢 Additions	0

Note
Break Check could not snapshot 1 subpath; the diff below excludes them.
@clerk/astro ./env: ambient declaration file (no top-level import or export): API Extractor can only analyze module entry points, so this global-augmentation surface cannot be snapshotted; add the subpath to ignoreSubpaths to acknowledge it (API Extractor: Unable to determine module for: /home/runner/_work/javascript/javascript/packages/astro/env.d.ts)

No API Changes Detected

All packages have stable APIs with no detected changes.

Report generated by Break Check

_{Last ran on 31b8867.}

feat(testing): log response diagnostics when FAPI retries are exhausted
31b8867

github-actionsBot added the testing label Jun 12, 2026

vercelBotdeployed to Preview – clerk-js-sandbox June 12, 2026 17:01 View deployment

vercelBotdeployed to Preview – swingset June 12, 2026 17:01 View deployment

wobsoriano approved these changes Jun 12, 2026
View reviewed changes

jacekradko merged commit e35b104 into mainJun 12, 2026
49 checks passed

jacekradko deleted the jacek/testing-429-diagnostics branch June 12, 2026 19:04

clerk-cookie mentioned this pull request Jun 12, 2026
ci(repo): Version packages #8836
Merged

feat(testing): log response diagnostics when FAPI retries are exhausted
31b8867

github-actionsBot added the testing label Jun 12, 2026

vercelBotdeployed to Preview – clerk-js-sandbox June 12, 2026 17:01 View deployment

vercelBotdeployed to Preview – swingset June 12, 2026 17:01 View deployment

wobsoriano approved these changes Jun 12, 2026
View reviewed changes

jacekradko merged commit e35b104 into mainJun 12, 2026
49 checks passed

jacekradko deleted the jacek/testing-429-diagnostics branch June 12, 2026 19:04

clerk-cookie mentioned this pull request Jun 12, 2026
ci(repo): Version packages #8836
Merged

feat(testing): log response diagnostics when FAPI retries are exhausted
31b8867

github-actionsBot added the testing label Jun 12, 2026

vercelBotdeployed to Preview – clerk-js-sandbox June 12, 2026 17:01 View deployment

vercelBotdeployed to Preview – swingset June 12, 2026 17:01 View deployment

wobsoriano approved these changes Jun 12, 2026
View reviewed changes

jacekradko merged commit e35b104 into mainJun 12, 2026
49 checks passed

jacekradko deleted the jacek/testing-429-diagnostics branch June 12, 2026 19:04

clerk-cookie mentioned this pull request Jun 12, 2026
ci(repo): Version packages #8836
Merged

feat(testing): log response diagnostics when FAPI retries are exhausted
31b8867

github-actionsBot added the testing label Jun 12, 2026

vercelBotdeployed to Preview – clerk-js-sandbox June 12, 2026 17:01 View deployment

vercelBotdeployed to Preview – swingset June 12, 2026 17:01 View deployment

wobsoriano approved these changes Jun 12, 2026
View reviewed changes

jacekradko merged commit e35b104 into mainJun 12, 2026
49 checks passed

jacekradko deleted the jacek/testing-429-diagnostics branch June 12, 2026 19:04

clerk-cookie mentioned this pull request Jun 12, 2026
ci(repo): Version packages #8836
Merged

feat(testing): log response diagnostics when FAPI retries are exhausted
31b8867

github-actionsBot added the testing label Jun 12, 2026

vercelBotdeployed to Preview – clerk-js-sandbox June 12, 2026 17:01 View deployment

vercelBotdeployed to Preview – swingset June 12, 2026 17:01 View deployment

wobsoriano approved these changes Jun 12, 2026
View reviewed changes

jacekradko merged commit e35b104 into mainJun 12, 2026
49 checks passed

jacekradko deleted the jacek/testing-429-diagnostics branch June 12, 2026 19:04

clerk-cookie mentioned this pull request Jun 12, 2026
ci(repo): Version packages #8836
Merged

feat(testing): log response diagnostics when FAPI retries are exhausted
31b8867

github-actionsBot added the testing label Jun 12, 2026

vercelBotdeployed to Preview – clerk-js-sandbox June 12, 2026 17:01 View deployment

vercelBotdeployed to Preview – swingset June 12, 2026 17:01 View deployment

wobsoriano approved these changes Jun 12, 2026
View reviewed changes

jacekradko merged commit e35b104 into mainJun 12, 2026
49 checks passed

jacekradko deleted the jacek/testing-429-diagnostics branch June 12, 2026 19:04

clerk-cookie mentioned this pull request Jun 12, 2026
ci(repo): Version packages #8836
Merged

feat(testing): log response diagnostics when FAPI retries are exhausted
31b8867

github-actionsBot added the testing label Jun 12, 2026

vercelBotdeployed to Preview – clerk-js-sandbox June 12, 2026 17:01 View deployment

vercelBotdeployed to Preview – swingset June 12, 2026 17:01 View deployment

wobsoriano approved these changes Jun 12, 2026
View reviewed changes

jacekradko merged commit e35b104 into mainJun 12, 2026
49 checks passed

jacekradko deleted the jacek/testing-429-diagnostics branch June 12, 2026 19:04

clerk-cookie mentioned this pull request Jun 12, 2026
ci(repo): Version packages #8836
Merged

feat(testing): log response diagnostics when FAPI retries are exhausted
31b8867

github-actionsBot added the testing label Jun 12, 2026

vercelBotdeployed to Preview – clerk-js-sandbox June 12, 2026 17:01 View deployment

vercelBotdeployed to Preview – swingset June 12, 2026 17:01 View deployment

wobsoriano approved these changes Jun 12, 2026
View reviewed changes

jacekradko merged commit e35b104 into mainJun 12, 2026
49 checks passed

jacekradko deleted the jacek/testing-429-diagnostics branch June 12, 2026 19:04

clerk-cookie mentioned this pull request Jun 12, 2026
ci(repo): Version packages #8836
Merged

Uh oh!

Conversation

jacekradko commented Jun 12, 2026• edited by coderabbitai BotLoading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary by CodeRabbit

Uh oh!

changeset-botBot commented Jun 12, 2026

🦋 Changeset detected

Uh oh!

vercelBot commented Jun 12, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

coderabbitaiBot commented Jun 12, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Uh oh!

pkg-pr-newBot commented Jun 12, 2026

Uh oh!

github-actionsBot commented Jun 12, 2026

API Changes Report

Summary

No API Changes Detected

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

jacekradko commented Jun 12, 2026• edited by coderabbitai BotLoading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary by CodeRabbit

Uh oh!

changeset-botBot commented Jun 12, 2026

🦋 Changeset detected

Uh oh!

vercelBot commented Jun 12, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

coderabbitaiBot commented Jun 12, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Uh oh!

pkg-pr-newBot commented Jun 12, 2026

Uh oh!

github-actionsBot commented Jun 12, 2026

API Changes Report

Summary

No API Changes Detected

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

jacekradko commented Jun 12, 2026• edited by coderabbitai BotLoading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary by CodeRabbit

Uh oh!

changeset-botBot commented Jun 12, 2026

🦋 Changeset detected

Uh oh!

vercelBot commented Jun 12, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

coderabbitaiBot commented Jun 12, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

jacekradko commented Jun 12, 2026•
edited by coderabbitai Bot
Loading

vercelBot commented Jun 12, 2026•
edited
Loading

coderabbitaiBot commented Jun 12, 2026•
edited
Loading

jacekradko commented Jun 12, 2026•
edited by coderabbitai Bot
Loading

vercelBot commented Jun 12, 2026•
edited
Loading

coderabbitaiBot commented Jun 12, 2026•
edited
Loading

jacekradko commented Jun 12, 2026•
edited by coderabbitai Bot
Loading

vercelBot commented Jun 12, 2026•
edited
Loading

coderabbitaiBot commented Jun 12, 2026•
edited
Loading

jacekradko commented Jun 12, 2026•
edited by coderabbitai Bot
Loading

vercelBot commented Jun 12, 2026•
edited
Loading

coderabbitaiBot commented Jun 12, 2026•
edited
Loading