Skip to content

chore: release main#973

Merged
packyg merged 4 commits intomainfrom
release-please--branches--main--changes--next
Apr 7, 2026
Merged

chore: release main#973
packyg merged 4 commits intomainfrom
release-please--branches--main--changes--next

Conversation

@stainless-app
Copy link
Copy Markdown
Contributor

@stainless-app stainless-app bot commented Apr 3, 2026

✨ Stainless prepared a new release

sdk: 0.84.0

0.84.0 (2026-04-07)

Full Changelog: sdk-v0.83.0...sdk-v0.84.0

Features

  • api: Add support for claude-mythos-preview (d4057b0)
  • tools: add AbortSignal support for tool runner (#848) (972d591)

This pull request is managed by Stainless's GitHub App.

The semver version number is based on included commit messages. Alternatively, you can manually set the version number in the title of this pull request.

For a better experience, it is recommended to use either rebase-merge or squash-merge when merging this pull request.

🔗 Stainless website
📚 Read the docs
🙋 Reach out for help or questions

@stainless-app stainless-app bot requested a review from a team as a code owner April 3, 2026 18:58
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch 3 times, most recently from 6a8ff40 to a7774d6 Compare April 6, 2026 05:41
dtmeadows and others added 2 commits April 6, 2026 10:13
## Summary

- Adds `AbortSignal` support to `BetaToolRunner` for cancelling API
calls and tool execution
- Introduces `BetaToolRunContext` type passed to `tool.run()` with
`signal` and `toolUseBlock`
- Adds `setRequestOptions()` method for updating signal/headers after
runner creation

## Context

Picks up the design from #877 (which was approved but stalled), adapted
to the current codebase. Multiple users have requested the ability to
cancel tool runner operations.

The signal flows through:
1. Constructor options or `setRequestOptions()` → stored in `#options`
2. `#options` passed to API calls (`messages.create`/`messages.stream`)
3. `generateToolResponse(signal?)` → `tool.run(input, { toolUseBlock,
signal })`

Tools can check `context?.signal?.aborted` or pass the signal to
downstream operations like `fetch()`.

## Test plan

- [x] `./scripts/build` passes
- [x] `./scripts/test -- tests/lib/tools/ToolRunner.test.ts` — 5 new
tests
- [x] Signal + toolUseBlock passed to tool.run via constructor options
- [x] Undefined signal when none provided
- [x] `setRequestOptions()` with direct object
- [x] `setRequestOptions()` with mutator function
- [x] Documentation updated in helpers.md

---------

Co-authored-by: Felix Becker <felix@anthropic.com>
Co-authored-by: stainless-app[bot] <142633134+stainless-app[bot]@users.noreply.github.com>
Co-authored-by: Mike Cluck <mcluck90@gmail.com>
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch 2 times, most recently from 01dada6 to 9c77666 Compare April 7, 2026 05:32
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 9c77666 to 52925b7 Compare April 7, 2026 17:47
@packyg packyg merged commit 4105fd6 into main Apr 7, 2026
11 checks passed
@packyg packyg deleted the release-please--branches--main--changes--next branch April 7, 2026 17:50
@stainless-app
Copy link
Copy Markdown
Contributor Author

stainless-app bot commented Apr 7, 2026

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants