ci(repo): Version Packages

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

clerk@2.0.0

Major Changes

• Remove the bundled clerk skill install command and install the clerk-cli agent skill from the clerk/skills repository during clerk init. (#315) by @wyattjoh

Minor Changes

• Add clerk api --fapi to call an instance's public Frontend API (e.g. clerk api --fapi /environment --app <id>). The FAPI host is resolved from the instance's publishable key, and the request is unauthenticated since these endpoints are public, which closes the loop on verifying config changes end to end with the CLI alone. (#345) by @rafa-thayto

• Refresh the visual style of prompts, lists, spinners, and intro/outro brackets to use @clack/prompts, and make interactive command endings reflect success, failure, or paused cancellation status. (#305) by @wyattjoh

• Add clerk impersonate (alias clerk imp) to create a short-lived sign-in URL that logs you in as another user, plus clerk impersonate revoke to cancel a pending token. Both require clerk login and stamp the impersonation with your account for auditing. (#373) by @rafa-thayto

• clerk init on Expo projects now installs the clerk-expo agent skill (Expo/React Native setup) alongside clerk-expo-patterns. The framework skill map supports multiple skills per framework. (#328) by @manovotny

• Render the "Next steps" header in a dusty mauve and sweep a white reflex highlight across it once after clerk deploy, clerk link, and clerk auth login, then settle on the flat color. The animation only runs on an interactive color terminal and falls back to plain styling when piped, in CI, or when NO_COLOR is set. (#322) by @rafa-thayto

• Add the clerk webhooks command group (V1): a PLAPI-free local webhooks toolkit. (#366) by @rafa-thayto

  • clerk webhooks listen — open a standalone Svix relay tunnel and forward deliveries to a local handler. No auth, no linked project, no backend. --forward-to is required. Without --token, the banner warns that the auto-generated relay token isn't a guaranteed-stable handle and prints the exact --token to pin next time; --token <c_…> pins an explicit, shareable URL. Flags: --forward-to (required), --token, --headers, --json. When --forward-to is missing, the usage error prints a runnable example beneath it.
  • clerk webhooks verify — verify a webhook signature offline (HMAC-SHA256), from a saved listen event line (--delivery) or the four explicit header values. No network calls.
  • clerk webhooks token — generate a valid relay token (c_ + 10 base62 chars) for listen --token. Prints the bare token to stdout so it pipes: clerk webhooks listen --token "$(clerk webhooks token)".

Patch Changes

• Keep a separator between the path and description in clerk api ls so long endpoint paths no longer run straight into their summaries. (#340) by @rafa-thayto

• Fix the OAuth provider walkthrough in clerk deploy printing the redirect URI on the wrong subdomain. Previously, the walkthrough showed https://accounts.{domain}/v1/oauth_callback, but the callback is served by the Frontend API, so pasting the value into a provider console caused redirect_uri_mismatch. The walkthrough now prints the instance's frontend_api_url (e.g. https://clerk.{domain}/v1/oauth_callback), matching the value shown in the Clerk Dashboard. (#335) by @Railly

• Only read stdin as --input-json when --input-json - is passed explicitly. Previously any piped stdin was consumed and parsed as the options payload, which broke shell loops (while read … | clerk …) and commands that read their own stdin (cat body.json | clerk api …) with a confusing invalid_json error. (#341) by @rafa-thayto

• Resolve the instance explicitly instead of silently defaulting to development: interactive flows (clerk impersonate, clerk impersonate revoke, clerk users open, the create wizard, and the application-picker fallback) now ask in human mode whenever the resolved app has more than one instance and no --instance flag pins one, and agent mode errors asking for an explicit --instance rather than defaulting — so the same command can't resolve a different instance depending on which instances the app happens to have. User lookups that find no match name the searched app and instance in the error, and instances targeted by raw ID are labeled by their environment type so the production impersonation warning always fires. (#373) by @rafa-thayto

• Print the "Next steps" list before sweeping the highlight across its header, so the animation no longer leaves a lone "Next steps" line that looks hung while the steps are hidden. (#343) by @rafa-thayto

• Fix clerk init for React Router v8 projects by adding @clerk/react-router to ssr.noExternal in the Vite config, preventing dev-mode SSR from failing with "useNavigate() may be used only in the context of a ". (#374) by @manovotny

• Stop showing the "possible sandboxed run" hint for ordinary network failures (unreachable host, VPN, DNS) in agent mode. The hint now requires a permission-like error before suggesting a sandbox, and is a single line. (#342) by @rafa-thayto