ci(repo): Version Packages - #419
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
8 times, most recently
from
August 21, 2026 20:21
600daf3 to
92e7c07
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 21, 2026 20:27
92e7c07 to
1fa707c
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@3.1.1
Patch Changes
Make the
clerk apiendpoint catalog discoverable from help output and 404 responses. (#430) by @shane-kerchevalapias "Call any Clerk API endpoint (200+;clerk api lsto browse)" instead of "Make authenticated requests to the Clerk API", andclerk api --helpexplains that this command covers what the dedicated commands do not.--platformnow explains that the Platform API has its own endpoint list,clerk api lsexamples say which API they list (they cover the Backend API, not every endpoint), andclerk api ls --platformis shown as an example.clerk api ls <keyword>on stderr, leaving stdout as the pipeable response body. The suggestion is scoped per surface:--platformappends that flag, and--fapigets none since it has no endpoint catalog.Report what was established when Ctrl-C interrupts
clerk deploy status, and record interrupted runs in usage telemetry. (#425) by @wyattjohclerk deploy statusno longer exits silently when the interrupt arrives before the deploy state is read. Agent mode emits a report withstate: "interrupted", which asserts nothing about the deploy.abortoutcome instead of no event at all.Report when signing out cannot revoke the session with Clerk, instead of always printing a clean sign-out. Local credentials are still removed either way, and
clerk auth logoutnow also warns whenCLERK_PLATFORM_API_KEYis set, since that key keeps authenticating requests. (#422) by @wyattjohRevoke the superseded session more reliably when re-authenticating: a transient error while checking the existing session no longer leaves the old session un-revoked, and a malformed
CLERK_OAUTH_BASE_URLno longer aborts sign-out partway through.Revoke the OAuth session with Clerk when signing out, so
clerk auth logoutends the session everywhere instead of only deleting the local credentials. Re-authenticating over an existing session now revokes the previous one as well. (#418) by @wyattjohStop a failing interrupt sequence from printing an unhandled rejection on Ctrl-C. (#436) by @wyattjoh
The SIGINT handler is async so it can await the telemetry flush that reports the interrupted run, but it was registered directly with
process.on, which discards a listener's return value. If anything in that sequence rejected — the lazy telemetry import, the flush itself — the failure surfaced as an unhandled rejection stack trace at the exact moment the user was trying to get their shell back, and the process never reached the signal death that a wrapping script reads. The registered listener is now a synchronous wrapper that exits by the route the interrupt calls for even when the sequence fails.Stop sending telemetry for
clerk completion. Shells re-run it on every startup when it is wired into an rc file, so its events measured shell startups rather than CLI usage. (#417) by @djgouldFix the exit code when a command is interrupted with Ctrl-C. Interrupting a command now exits 130 by terminating on SIGINT rather than calling
process.exit(130), so a wrapping shell script sees a real signal death and stops as expected, and the interrupted run is reported to telemetry instead of going unrecorded. This covers in-flight requests, poll intervals and retry backoffs, project generators run byclerk init, andclerk webhooks listenonce it has drained. Ctrl-C while the CLI is only waiting on you — at a prompt, during browser sign-in, or in$EDITOR— still exits 0. (#420) by @wyattjohKeep
--define CLI_VERSIONworking when building with Bun 1.4. (#435) by @rafa-thaytoBun 1.4 runs macros in a sealed transpiler context that
--defineglobals no longer reach, so the version macro silently fell back to the checkout-derived dev version even when a release version was injected. The define check and dev classification now live inversion.tsmodule scope, where define substitution still applies; the macro only derives the Git checkout fallback.Stop the "Update available" notice from garbling the "Next steps" block. (#435) by @rafa-thayto
The next-steps outro animation moves the cursor back onto the header line for ~450ms, but several commands (
switch-env,auth logout,unlink,users create,apps create, and others) did not await it. The command's promise resolved mid-animation, so the post-command update check printed its notice at the parked cursor position — overwriting the step lines and leaving a stray duplicate "Next steps" header. Everyoutro(...)call is now awaited, so output printed after a command lands below the finished block.