fix(clerk-js): Do not allow setActive({ organization: null }) when organization selection is forced

[LauraBeatris]

Description

Resolves ORGS-682

Disclaimer: We're also going to apply protections on the API side, this is just an additional guard.

Introduces an error guard not to allow calling setActive({ organization: null }) when organization selection is forced on the instance settings.

The same handling should be made when we refactor setActive to setCurrent 👀

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: 5dd6089

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/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 Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
clerk-js-sandbox	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 6, 2025 9:50pm

[pkg-pr-new]

Open in StackBlitz

@clerk/agent-toolkit

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

@clerk/astro

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

@clerk/backend

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

@clerk/chrome-extension

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

@clerk/clerk-js

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

@clerk/dev-cli

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

@clerk/elements

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

@clerk/clerk-expo

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

@clerk/expo-passkeys

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

@clerk/express

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

@clerk/fastify

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

@clerk/localizations

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

@clerk/nextjs

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

@clerk/nuxt

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

@clerk/clerk-react

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

@clerk/react-router

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

@clerk/remix

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

@clerk/shared

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

@clerk/tanstack-react-start

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

@clerk/testing

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

@clerk/themes

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

@clerk/types

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

@clerk/upgrade

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

@clerk/vue

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

commit: c6cf838

[LauraBeatris]

Some integration tests started to fail after introducing this guard, so I'll deeper tomorrow while also adding error handling on FAPI side.