Skip to content

Conversation

@stainless-app
Copy link
Contributor

@stainless-app stainless-app bot commented Jan 13, 2026

Automated Release PR

0.3.0 (2026-01-28)

Full Changelog: v0.2.0...v0.3.0

Features

  • client: add support for binary request streaming (48f4cca)

Bug Fixes

  • api: default auth server (38c637a)
  • docs: fix mcp installation instructions for remote servers (e4e3619)

Chores

  • ci: upgrade actions/github-script (cf53a9e)
  • internal: update actions/checkout version (c72dfca)

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


Note

Release 0.3.0 introducing a new OCR API and improved client I/O.

  • New API: Adds client.ocr.process for /v1/ocr with OcrDocument, OcrResponse, docs (api.md), and tests
  • Client I/O: Supports raw/binary request streaming via new content param (sync/async); deprecates passing raw bytes in body; adds BinaryTypes/AsyncBinaryTypes; request builder prevents mixing content with json/files
  • Retries: Default max_retries increased to 2 with backoff tuned (INITIAL_RETRY_DELAY=0.5, MAX_RETRY_DELAY=8.0); README updated
  • Auth defaults: Sets default as_base_url to https://as.dedaluslabs.ai when env var is unset
  • Types cleanup: Function/tool JSON schema params now plain dicts (no JSONObjectInput) across request/response formats
  • CI/Docs: Bumps actions/checkout to v6 and actions/github-script to v8; README MCP install links fixed
  • Release metadata: Version bump to 0.3.0, changelog, manifest, stats updated (endpoints: 10→11)

Written by Cursor Bugbot for commit 120f4f7. This will update automatically on new commits. Configure here.

@stainless-app
Copy link
Contributor Author

stainless-app bot commented Jan 13, 2026

🧪 Testing

To try out this version of the SDK, run:

pip install 'https://pkg.stainless.com/s/dedalus-sdk-python/e4e3619990099b43df78e88415e3627daf8c7425/dedalus_labs-0.2.0-py3-none-any.whl'

Expires at: Fri, 27 Feb 2026 16:37:39 GMT
Updated at: Wed, 28 Jan 2026 16:37:39 GMT

@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from ac5c5d9 to c72a9be Compare January 16, 2026 18:31
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from c72a9be to 00246c5 Compare January 22, 2026 03:58
Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.

*,
cast_to: Type[ResponseT],
body: Body | None = None,
content: BinaryTypes | None = None,
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Iterator content silently lost on request retry

Medium Severity

When content is an Iterable[bytes] (like a generator), the iterator is consumed on the first request attempt. If a retryable error occurs, the retry logic uses model_copy which performs a shallow copy, so options.content still references the same exhausted iterator. Subsequent retry attempts send an empty request body. This is exacerbated by DEFAULT_MAX_RETRIES being increased from 0 to 2 in this same PR. Users passing generator-based content could experience silent data loss on transient failures.

Additional Locations (1)

Fix in Cursor Fix in Web

@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 00246c5 to f4bfcf4 Compare January 23, 2026 18:15
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from f4bfcf4 to 120f4f7 Compare January 28, 2026 16:37
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.

0 participants