Repository navigation
ci(repo): Version Packages - #597
Open
github-actions[bot] wants to merge 1 commit into
Open
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
October 30, 2026 19:59
072b2e1 to
f3875d4
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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@4.1.1
Patch Changes
Stop calling a claimed application "unclaimed accountless" when
clerk configreaches it with only a secret key. WithCLERK_SECRET_KEY(or a key in.env) and no--appor linked profile, aclerk config patch,put,schemaor--instancerefusal, aclerk enable billing/clerk disable billingrefusal, or aclerk users open <user-id>refusal, now asks Clerk whether the application belongs to an account. If it does, it says a secret key can't change those settings, and to pass--app <id> --instance <dev|prod>(or runclerk link) withclerk auth loginorCLERK_PLATFORM_API_KEY; a login alone isn't enough while the secret key is set. If Clerk can't say, the message covers both cases. A defaultclerk config pullof a claimed application warns what the secret key left out. (#545) by @royangerCheck
clerk migrate importagainst the user limit Clerk reports for the instance, so a development instance Clerk has raised no longer rejects users it has room for.CLERK_MIGRATE_DEV_USER_LIMITis now only a fallback for when Clerk doesn't report a limit, and--jsonsays where the limit came from.clerk migrateis still experimental and needsCLERK_EXPERIMENTAL=migrate. (#552) by @royanger