chore: version packages - #372
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
September 24, 2026 10:22
023e36f to
2cea2a8
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
September 24, 2026 10:38
2cea2a8 to
50df7d8
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
September 24, 2026 10:46
50df7d8 to
988f63b
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
September 24, 2026 11:02
988f63b to
a1cc3f4
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
September 24, 2026 11:30
a1cc3f4 to
0bb377f
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
September 24, 2026 15:09
0bb377f to
4607d48
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
September 24, 2026 15:27
4607d48 to
9de4633
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
September 24, 2026 15:39
9de4633 to
da87d48
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
September 24, 2026 15:55
da87d48 to
95b80fd
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
September 24, 2026 16:08
95b80fd to
c561e7f
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
September 24, 2026 16:24
c561e7f to
0b248e4
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
September 24, 2026 21:31
0b248e4 to
d66b424
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
September 24, 2026 21:49
d66b424 to
3b612ca
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
September 24, 2026 23:09
3b612ca to
6be871f
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
September 25, 2026 13:08
6be871f to
73273fd
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
September 25, 2026 18:18
73273fd to
ae1d952
Compare
This branch was successfully deployed
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 the packages will be published to npm 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
@cycgraph/orchestrator@1.6.0
Minor Changes
effortfield ('low'|'medium'|'high'|'xhigh'|'max'). The executor translates it to the provider's own option at call time — Anthropiceffort, OpenAIreasoningEffort— for agent, supervisor, evaluator, and extractor calls alike; providers without an effort control ignore it, and an explicit value insideproviderOptionsstill wins. The field threads through the authoring facade (agent({ effort })), both registries, graph bundles, and a new nullableeffortcolumn on the Postgresagentstable (migration 0021). Bundling also stops droppingmax_output_tokensfrom embedded agents, whichBundledAgentSchemahad been silently stripping.Patch Changes
max_retries: thea2anode now forwards it to the client, and@cycgraph/a2aretries a failed connection (Agent Card resolution and client construction) with exponential backoff within the task timeout.message/sendis never retried, because a resend could start the remote task twice.a2anode whose remote task is still running when its wait bound fires now logsa2a_task_pendingwith thetask_idinstead ofa2a_transport_failed, so logs no longer report a live remote task as a transport failure.timeout_msis now enforced: thea2anode passes it asrequestTimeoutMs, and@cycgraph/a2aapplies it to each connection attempt and status poll on its own. A remote that stalls one of those calls now fails fast instead of holding the node for the fulltask_timeout_ms; the blockingmessage/sendstays bounded bytask_timeout_msonly, so long-running remote tasks are unaffected.GraphRunner.cancel()could be followed by fresh LLM calls from backoff retries, sorun()kept going long after cancellation.token_usagelog line now carriesmodel, the concrete model the call ran on after tier resolution, so per-model spend is readable from a run log.@cycgraph/orchestrator-postgres@4.2.0
Minor Changes
effortfield ('low'|'medium'|'high'|'xhigh'|'max'). The executor translates it to the provider's own option at call time — Anthropiceffort, OpenAIreasoningEffort— for agent, supervisor, evaluator, and extractor calls alike; providers without an effort control ignore it, and an explicit value insideproviderOptionsstill wins. The field threads through the authoring facade (agent({ effort })), both registries, graph bundles, and a new nullableeffortcolumn on the Postgresagentstable (migration 0021). Bundling also stops droppingmax_output_tokensfrom embedded agents, whichBundledAgentSchemahad been silently stripping.@cycgraph/tools@1.6.0
Minor Changes
listReviewThreadsnow returns each thread's whole conversation, not only its first comment: every comment's author, association, body, and timestamp, plus the thread's current and original line, whether it is outdated, and the diff hunk it was left on.prFeedbacktags each comment with itssource(review body, conversation, or inline) andcreatedAt, so a caller can tell feedback that arrived after a given point.submitPrReviewtakes an optionalbodyWithoutComments, submitted instead ofbodywhen the API rejects the inline comments, for a caller whose body leaves out what those comments carry. NewcommentOnPrFilecomments on a whole file of a pull request, opening a review thread that can be replied to and resolved like a line comment.@cycgraph/a2a@1.1.9
Patch Changes
max_retries: thea2anode now forwards it to the client, and@cycgraph/a2aretries a failed connection (Agent Card resolution and client construction) with exponential backoff within the task timeout.message/sendis never retried, because a resend could start the remote task twice.submitted/workingwhenmax_wait_msruns out or the run is aborted is no longer reported asfailed; the delivery now rejects with a non-retryableA2ATaskPendingErrorcarrying the task id, so the node's failure policy no longer starts a duplicate remote task while the first keeps running.Requestinput's own headers (such asContent-TypeandAccept) on every A2A request hop, including redirect replays. Before this fix, fetch dropped them because the per-server headers were always passed throughinit.headers. The merge order is now theRequest's headers, then the SDK'sinit.headers, then the per-server headers.timeout_msis now enforced: thea2anode passes it asrequestTimeoutMs, and@cycgraph/a2aapplies it to each connection attempt and status poll on its own. A remote that stalls one of those calls now fails fast instead of holding the node for the fulltask_timeout_ms; the blockingmessage/sendstays bounded bytask_timeout_msonly, so long-running remote tasks are unaffected.@cycgraph/context-engine@0.7.6
Patch Changes
@cycgraph/evals@0.3.4
Patch Changes
runOrchestratorSutnow cancels a run that exceedstimeoutMsand waits for it to settle before returning. A timed-out trajectory can no longer keep making LLM and tool calls in the background while the next test reconfigures the process-global agent factory and provider registry.