Repository navigation
chore: version packages - #478
Merged
Merged
Conversation
Deploying herdctl with
|
| Latest commit: |
c93fc07
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://f314a63a.herdctl.pages.dev |
| Branch Preview URL: | https://changeset-release-main.herdctl.pages.dev |
Contributor
|
Important Review skippedBot user detected. To trigger a single review, invoke the
 |
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
@herdctl/core@5.34.1
Patch Changes
4065fdeThanks @edspencer! - Reap a managed session whose turn was interrupted. Claude Code does not fire itsStophook on a user interrupt, so the session reaper never learned the turn had ended: theclaudesubprocess leaked, and the next resume of that session waited out the full 5-minute openChatSession(resume) spawns a second subprocess for an already-live session → SDK self-interrupt (double-resume class) #403 defer ceiling before spawning anyway. The stream tap now emits aturn_abortedsignal when a turn'sresultarrives without itsStophook. It carries the last background-task set seen on the stream, and the reaper keeps or reaps on that (without reconciling crons).