🦋 New version release#112
Merged
Merged
Conversation
9384305 to
cdd02ad
Compare
cdd02ad to
6198076
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
@smooai/[email protected]
Patch Changes
th api keysfirst-class for both auth-client types.createnow takes structured--type m2m|b2mand repeatable--allowed-originflags (B2M requires ≥1 origin, validated client-side) instead of a hand-written raw JSON body;update <id> --allowed-origin …replaces a B2M client's origin allowlist (PATCH, B2M-only); a newrotate <id>mints a replacement of the same type/origins then revokes the old one (the API has no in-place rotation, so the replacement is created first and the new client id + key are shown once). Adds accurate help (M2M secret vs B2M publishable, both shown once),--jsonon reads, and--org-id [aliases: --org]. The raw--bodyescape hatch stays. Fixes a latent bug: these routes require a dashboard user session (auth.provider === 'supabase', 403 under M2M), so the surface now uses the user-JWTUserClientrather than the M2M-capable client. (pearl th-8d2a41)thCLI audit quick-wins (non-breaking). Standardized the org-override flag to--org-idwith--orgas a visible alias across everyth api *leaf (agents, members, knowledge, jobs, products, observability, crm, testing — ~41 args), retiring the--organd--organization-idspellings. Filled ~100 previously-blank--helpdoc strings on subcommand variants and args (the wholeth api *andth testing *CRUD surface, includingth testing's runs/cases/environments/deployments groups). Gave the operative-control commands (th pause/resume/steer/cancel/approve) a proper<OPERATIVE_ID>metavar + arg help (was the stale<BEAD_ID>), clarifiedth inboxvsth msg inbox, fixed the lowercaseth api jobs list --typemetavar, wrote accurate descriptions forth db/th project/th jira/th web/th tailscale, and scrubbed staleth api orgs switch/--orgreferences fromth org switchhelp. No behavior or signature changes. (pearls th-c153ec follow-up; from the th-CLI audit)