Skip to content

chore: version packages - #372

Merged
wmcmahan merged 1 commit into
mainfrom
changeset-release/main
Sep 25, 2026
Merged

wmcmahan merged 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Sep 24, 2026 •

Copy link
Copy Markdown
Contributor

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

  • 75642e7: Agent configs gain a provider-neutral effort field ('low' | 'medium' | 'high' | 'xhigh' | 'max'). The executor translates it to the provider's own option at call time — Anthropic effort, OpenAI reasoningEffort — for agent, supervisor, evaluator, and extractor calls alike; providers without an effort control ignore it, and an explicit value inside providerOptions still wins. The field threads through the authoring facade (agent({ effort })), both registries, graph bundles, and a new nullable effort column on the Postgres agents table (migration 0021). Bundling also stops dropping max_output_tokens from embedded agents, which BundledAgentSchema had been silently stripping.

Patch Changes

  • 042d9b2: Honor the A2A registry entry's max_retries: the a2a node now forwards it to the client, and @cycgraph/a2a retries a failed connection (Agent Card resolution and client construction) with exponential backoff within the task timeout. message/send is never retried, because a resend could start the remote task twice.
  • 4ac1d2b: An a2a node whose remote task is still running when its wait bound fires now logs a2a_task_pending with the task_id instead of a2a_transport_failed, so logs no longer report a live remote task as a transport failure.
  • c42b3d6: The A2A registry entry's timeout_ms is now enforced: the a2a node passes it as requestTimeoutMs, and @cycgraph/a2a applies 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 full task_timeout_ms; the blocking message/send stays bounded by task_timeout_ms only, so long-running remote tasks are unaffected.
  • 8cbfbce: Stop retrying a failed node once the workflow has been cancelled or has timed out. Before this fix, GraphRunner.cancel() could be followed by fresh LLM calls from backoff retries, so run() kept going long after cancellation.
  • c43e1fa: The agent executor's token_usage log line now carries model, 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

  • 75642e7: Agent configs gain a provider-neutral effort field ('low' | 'medium' | 'high' | 'xhigh' | 'max'). The executor translates it to the provider's own option at call time — Anthropic effort, OpenAI reasoningEffort — for agent, supervisor, evaluator, and extractor calls alike; providers without an effort control ignore it, and an explicit value inside providerOptions still wins. The field threads through the authoring facade (agent({ effort })), both registries, graph bundles, and a new nullable effort column on the Postgres agents table (migration 0021). Bundling also stops dropping max_output_tokens from embedded agents, which BundledAgentSchema had been silently stripping.

@cycgraph/tools@1.6.0

Minor Changes

  • 8ffc7fd: listReviewThreads now 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. prFeedback tags each comment with its source (review body, conversation, or inline) and createdAt, so a caller can tell feedback that arrived after a given point. submitPrReview takes an optional bodyWithoutComments, submitted instead of body when the API rejects the inline comments, for a caller whose body leaves out what those comments carry. New commentOnPrFile comments 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

  • 042d9b2: Honor the A2A registry entry's max_retries: the a2a node now forwards it to the client, and @cycgraph/a2a retries a failed connection (Agent Card resolution and client construction) with exponential backoff within the task timeout. message/send is never retried, because a resend could start the remote task twice.
  • 4ac1d2b: A remote task still submitted/working when max_wait_ms runs out or the run is aborted is no longer reported as failed; the delivery now rejects with a non-retryable A2ATaskPendingError carrying the task id, so the node's failure policy no longer starts a duplicate remote task while the first keeps running.
  • d2aeb73: Keep a Request input's own headers (such as Content-Type and Accept) on every A2A request hop, including redirect replays. Before this fix, fetch dropped them because the per-server headers were always passed through init.headers. The merge order is now the Request's headers, then the SDK's init.headers, then the per-server headers.
  • c42b3d6: The A2A registry entry's timeout_ms is now enforced: the a2a node passes it as requestTimeoutMs, and @cycgraph/a2a applies 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 full task_timeout_ms; the blocking message/send stays bounded by task_timeout_ms only, so long-running remote tasks are unaffected.

@cycgraph/context-engine@0.7.6

Patch Changes

  • 63297fa: The incremental pipeline no longer throws on the second and later turns when a per-segment stage removes a segment. Removed segments are left out of the ordered output, and an unchanged removed segment is now served from cache instead of being compressed again.

@cycgraph/evals@0.3.4

Patch Changes

  • 8cbfbce: runOrchestratorSut now cancels a run that exceeds timeoutMs and 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.
  • Updated dependencies [042d9b2]
  • Updated dependencies [4ac1d2b]
  • Updated dependencies [c42b3d6]
  • Updated dependencies [75642e7]
  • Updated dependencies [63297fa]
  • Updated dependencies [8cbfbce]
  • Updated dependencies [c43e1fa]
    • @cycgraph/orchestrator@1.6.0
    • @cycgraph/context-engine@0.7.6

@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 023e36f to 2cea2a8 Compare September 24, 2026 10:22
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 2cea2a8 to 50df7d8 Compare September 24, 2026 10:38
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 50df7d8 to 988f63b Compare September 24, 2026 10:46
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 988f63b to a1cc3f4 Compare September 24, 2026 11:02
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from a1cc3f4 to 0bb377f Compare September 24, 2026 11:30
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 0bb377f to 4607d48 Compare September 24, 2026 15:09
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 4607d48 to 9de4633 Compare September 24, 2026 15:27
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 9de4633 to da87d48 Compare September 24, 2026 15:39
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from da87d48 to 95b80fd Compare September 24, 2026 15:55
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 95b80fd to c561e7f Compare September 24, 2026 16:08
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from c561e7f to 0b248e4 Compare September 24, 2026 16:24
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 0b248e4 to d66b424 Compare September 24, 2026 21:31
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from d66b424 to 3b612ca Compare September 24, 2026 21:49
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 3b612ca to 6be871f Compare September 24, 2026 23:09
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 6be871f to 73273fd Compare September 25, 2026 13:08
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 73273fd to ae1d952 Compare September 25, 2026 18:18
@wmcmahan
wmcmahan merged commit 0f7734f into main Sep 25, 2026
17 checks passed
@wmcmahan
wmcmahan deleted the changeset-release/main branch September 25, 2026 19:18

This branch was successfully deployed

1 active deployment
Preview — ae1d952b Deployed Sep 25, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant