chore: version packages#59
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
July 10, 2026 20:46
1434723 to
9e4a957
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
@taskless/cli@0.10.0
Minor Changes
da74920: Send an
x-taskless-cli-versionheader on every request to the Taskless service (rule generation, reconcile,whoami, and the device-auth flow) declaring the CLI's version. The service uses this to gate capability-dependent responses — notably runtime rules — on the CLI being new enough to handle them; a request without the header is treated as a pre-runtime CLI. The version is also emitted with the CLI's telemetry so usage is recorded client-side rather than inferred server-side.19f4327: Send the acting organization's identity on every write request. The CLI now resolves which Taskless org owns the current repository by matching the repo's git remotes (
origin→upstream→ rest) against the canonical owner URLs returned bywhoami, and sends that org's Taskless UUID as the subject on rule generation, iterate, and reconcile calls. This fixes multi-org users being routed to whichever org their token happened to pin; the server authorizes the chosen org per request. When no remote matches a known org, the CLI falls back to the token's numericorgIdclaim, so single-org behavior is unchanged.The client-side owner-URL canonicalizer is a verbatim port of the server's shared implementation, so both sides compare by exact string equality across SSH,
ssh:///git://, port, andwww.remote forms.rule create/rule improvenow handle two additional generation states:classifying(a transient pre-build phase) andunsupported, a terminal state emitted when the request needs a capability the organization's plan doesn't include (for example, runtime rules) — surfaced with a clear message and the newRULE_UNSUPPORTEDerror code. When the server can't act on a repository for the selected org (its GitHub App installation doesn't cover the repo, or membership changed), the CLI now explains the coverage cause rather than only suggesting re-authentication.f392880: Add server-owned rule reconciliation and runtime rules to
taskless check. Authenticated runs reconcile the repo's rules against the Taskless service and execute only the server-blessed set. A new class of runtime rules (.taskless/runtime-rules/— one or more ast-grep capture rules plus acheck.tsassertion) runs through a local harness: the capture rules narrow with ast-grep, and only on a match ischeck.tsinvoked via a bundledtsx. Becausecheck.tsis arbitrary code, it runs only when its signature is validated by the server; otherwise it is skipped and reported. Adds the--dangerously-run-scripts(run runtime rules unverified) and--timeoutflags.(Backfills the changeset that was missed when this work landed across feat(cli): server-owned rule reconciliation #47, docs(openspec): propose runtime rule execution #49, and feat(cli): implement runtime rule execution #50.)