fix(clerk-js): include ticket strategy in future helpers

[jeremy-clerk]

Description

Fixes#8219.

signIn.ticket() and signUp.ticket() were only sending ticket to FAPI. Ticket flows need strategy: 'ticket' as well, otherwise the request succeeds but the ticket is not applied.

This updates the Core 3 future helpers to send the same shape the prebuilt UI already uses.

Verified with:

• pnpm exec vitest run src/core/resources/__tests__/SignIn.test.ts src/core/resources/__tests__/SignUp.test.ts
• pnpm exec vitest run src/core/resources/__tests__/SignIn.test.ts -t "resetPassword|ResetPassword"

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:

[changeset-bot]

🦋 Changeset detected

Latest commit: 5625dc3

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

This PR includes changesets to release 3 packages

Name	Type
@clerk/clerk-js	Patch
@clerk/chrome-extension	Patch
@clerk/expo	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]

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

Project	Deployment	Actions	Updated (UTC)
clerk-js-sandbox	Ready	Preview, Comment	May 26, 2026 2:42pm

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR adds explicit strategy: 'ticket' parameter passing to the ticket-based sign-in and sign-up helpers in @clerk/clerk-js. The SignInFuture.ticket() and SignUpFuture.ticket() methods now pass both strategy: 'ticket' and the ticket value to their respective create() calls, replacing the prior behavior of only forwarding the ticket field. The test suites are updated to verify this behavior across multiple scenarios, including query-parameter-derived tickets, explicitly provided tickets, and edge cases where an alternate strategy is overridden. A changeset documents the patch-level update.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
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.
Description check	✅ Passed	The pull request description clearly relates to the changeset, explaining the bug fix of adding the missing strategy field to ticket() methods.
Title check	✅ Passed	The title accurately reflects the main change: explicitly including the ticket strategy parameter in the SignIn and SignUp future helpers.

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

---

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

[pkg-pr-new]

Open in StackBlitz

@clerk/astro

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

@clerk/backend

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

@clerk/chrome-extension

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

@clerk/clerk-js

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

@clerk/dev-cli

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

@clerk/expo

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

@clerk/expo-passkeys

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

@clerk/express

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

@clerk/fastify

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

@clerk/hono

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

@clerk/localizations

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

@clerk/nextjs

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

@clerk/nuxt

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

@clerk/react

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

@clerk/react-router

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

@clerk/shared

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

@clerk/tanstack-react-start

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

@clerk/testing

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

@clerk/ui

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

@clerk/upgrade

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

@clerk/vue

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

commit: 5625dc3

[wobsoriano]

This looks legit to me and minimal. In validateAndRetrieveStrategy (FAPI sign-in service), when strategy is nil and no password is present, it returns nil immediately and the ticket param is never read. Ticket requires to be explicit.

The prebuilt UI has it right (SignInStart)

cc @dstaley

[jeremy-clerk]

@wobsoriano or @dstaley can you merge this for me when ready, I don't have perms 🙏