Skip to content

chore: version packages - #492

Merged
edspencer merged 1 commit into
mainfrom
changeset-release/main
Nov 14, 2026
Merged

edspencer merged 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Nov 14, 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

@herdctl/core@5.34.2

Patch Changes

  • #472 e852a99 Thanks @edspencer! - Raise the @anthropic-ai/claude-agent-sdk floor to ^0.3.302 (current npm latest).

    Picks up upstream fixes across 0.3.284–0.3.302, including: foreground subagents missing task-tracking tools, SDK MCP tool schema conversion, toggleMcpServer() leaving in-process tool calls hung, forkSession() history reading, getSessionMessages() message inclusion, importSessionToStore dropping transcript rows containing U+2028/U+2029, assistant text blocks losing citations in streamed responses, and includePartialMessages streams never emitting message_stop on a cut stream.

    No code adaptation was needed. The API surface is additive over this range — the only new exports are BUILTIN_TOOL_NAMES and LEGACY_TOOL_NAME_ALIASES, and nothing was removed or renamed. Two upstream permissionMode default changes (0.3.286 and 0.3.302) do not reach herdctl, which always sets permissionMode explicitly (agent.permission_mode ?? "acceptEdits") and always passes --permission-mode on the CLI runtime.

    Note one runtime behaviour change inherited from 0.3.302: fork subagents (subagent_type: "fork") are now on by default in SDK sessions, matching the terminal. Set CLAUDE_CODE_FORK_SUBAGENT=0 to opt out.

  • #493 82a4997 Thanks @edspencer! - Raise the @anthropic-ai/claude-agent-sdk floor to ^0.3.325 (current npm latest, bundling Claude Code 2.1.325).

    The bundled Claude Code version is what gates new models: the API refuses a model whose minimum client version is newer than the CLI making the request, answering 400 claude_code_version_too_old (Claude Fable 5.2 needs 2.1.290 or newer). On the SDK runtime the CLI is the SDK's own bundled binary, not the claude on PATH, so a consumer cannot fix this by upgrading Claude Code — only by resolving a newer SDK. Raising the floor makes every consumer that installs this release resolve a binary new enough for the current model lineup.

    No code adaptation was needed: none of the APIs changed across 0.3.303–0.3.325 are used by herdctl. Behaviour changes worth knowing about if you configure permissions yourself:

    • 0.3.325: read-only git commands now go through the permission flow instead of being auto-approved, and sandboxed Bash commands are no longer auto-approved unless autoAllowBashIfSandboxed: true. An agent whose allowed_tools includes Bash is unaffected. Deny rules now also remove in-process SDK MCP tools from Claude's tool list, as they always should have.
    • 0.3.317: the file_unchanged variant of FileReadOutput was removed.
    • 0.3.311: minimum Node.js raised to 18.14.0.

@github-actions
github-actions Bot requested a review from edspencer as a code owner November 14, 2026 12:23
@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Nov 14, 2026 •

Copy link
Copy Markdown

Deploying herdctl with  Cloudflare Pages  Cloudflare Pages

Latest commit: 00888c0
Status: ✅  Deploy successful!
Preview URL: https://ab74e9a0.herdctl.pages.dev
Branch Preview URL: https://changeset-release-main.herdctl.pages.dev

View logs

@coderabbitai

coderabbitai Bot commented Nov 14, 2026 •

Copy link
Copy Markdown
Contributor

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 071d7111-c8e3-4417-aa81-a02bcd620807

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 81be113 to 681a440 Compare November 14, 2026 12:28
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 681a440 to 8358459 Compare November 14, 2026 17:32
edspencer pushed a commit that referenced this pull request Nov 14, 2026
…happen

The first pass fixed the three tests seen failing on #492, and CI promptly
failed a fourth: "triggers cron schedules when time is within trigger
window", whose wait(500) had already been raised once "for slow CI runners".
The flake is the pattern, not those three tests: any fixed sleep followed by
an assertion that the scheduler got somewhere can lose on a busy runner.

Every positive-condition sleep in scheduler.test.ts now polls (21 more).
Sleeps that prove an ABSENCE (no second trigger, nothing after stop, max
concurrency never exceeded) stay fixed, now after a waitUntil for the event
they measure from. waitUntil's deadline drops to 4s, under vitest's 5s test
timeout, so a real failure reports the helper's message.

Mutation-checked: disabling the cron trigger window fails both window tests
in 4s with "waitUntil: condition not met"; they neither hang nor pass.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
edspencer pushed a commit that referenced this pull request Nov 14, 2026
docker-security.test.ts "Container Configuration" shells out to the real
Docker daemon (docker create / inspect / rm). On a cold or busy CI runner a
single `docker create` can exceed vitest's 5s default: "sets memory limits"
and "sets user to non-root" both timed out that way on #492, with the other
3772 tests green. Size the per-test timeout for real Docker on that block
only; the pure-config tests elsewhere in the file keep the default.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
edspencer added a commit that referenced this pull request Nov 14, 2026
…ontainer tests (#494)

* test(core): poll instead of sleeping in three scheduler timing tests

Three scheduler tests waited a fixed wait(300)/wait(100)/wait(50) and then
asserted the scheduler had already checked, triggered, run and persisted
state.yaml. On a loaded CI runner the guess is sometimes short: all three
failed on the #492 version PR (both attempts) and on e852a99, and
scheduler.test.ts failures recur in older CI runs too, while the behaviour
under test was fine.

Replace those sleeps with waitUntil(), which polls the same condition up to
a 5s deadline. The deadline uses performance.now(): two of these tests freeze
Date.now to pin the cron clock, so a Date.now deadline would never expire.
Assertions are unchanged; the tests only wait as long as they need to.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* test(core): poll in every scheduler test that waits for something to happen

The first pass fixed the three tests seen failing on #492, and CI promptly
failed a fourth: "triggers cron schedules when time is within trigger
window", whose wait(500) had already been raised once "for slow CI runners".
The flake is the pattern, not those three tests: any fixed sleep followed by
an assertion that the scheduler got somewhere can lose on a busy runner.

Every positive-condition sleep in scheduler.test.ts now polls (21 more).
Sleeps that prove an ABSENCE (no second trigger, nothing after stop, max
concurrency never exceeded) stay fixed, now after a waitUntil for the event
they measure from. waitUntil's deadline drops to 4s, under vitest's 5s test
timeout, so a real failure reports the helper's message.

Mutation-checked: disabling the cron trigger window fails both window tests
in 4s with "waitUntil: condition not met"; they neither hang nor pass.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* test(core): give the real-Docker container tests a 30s budget

docker-security.test.ts "Container Configuration" shells out to the real
Docker daemon (docker create / inspect / rm). On a cold or busy CI runner a
single `docker create` can exceed vitest's 5s default: "sets memory limits"
and "sets user to non-root" both timed out that way on #492, with the other
3772 tests green. Size the per-test timeout for real Docker on that block
only; the pure-config tests elsewhere in the file keep the default.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: HomeLab Agent <homelab-infra@valfenda.net>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 8358459 to 00888c0 Compare November 14, 2026 17:50
@edspencer edspencer closed this Nov 14, 2026
@edspencer edspencer reopened this Nov 14, 2026
@edspencer
edspencer merged commit da1f2ec into main Nov 14, 2026
8 checks passed
@edspencer
edspencer deleted the changeset-release/main branch November 14, 2026 18:23
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