release: 1.11.0

[stainless-app]

Automated Release PR

1.11.0 (2026-02-03)

Full Changelog: v1.10.0...v1.11.0

Features

• api: api update (98c6790)
• api: api update (0494c61)
• api: api update (f98c6d3)
• api: api update (60e16d2)
• client: add custom JSON encoder for extended type support (9c2e7bf)
• client: add support for binary request streaming (6fa872f)

Bug Fixes

• compat with Python 3.14 (4453f62)
• compat: update signatures of model_dump and model_dump_json for Pydantic v1 (d4527cf)
• ensure streams are always closed (e4be19e)
• types: allow pyright to infer TypedDict types within SequenceNotStr (6834686)
• use async_to_httpx_files in patch method (855d52c)

Chores

• add missing docstrings (d834791)
• add Python 3.14 classifier and testing (8c6d5c5)
• ci: upgrade actions/github-script (48d3629)
• deps: mypy 1.18.1 has a regression, pin to 1.17 (0c9e340)
• docs: use environment variables for authentication in code snippets (de0cde1)
• internal: add --fix argument to lint script (461ab0b)
• internal: add missing files argument to base client (eb32a75)
• internal: update actions/checkout version (e003383)
• package: drop Python 3.8 support (d68084f)
• speedup initial import (12abf0c)
• update lockfile (d0dae69)

Documentation

• add more examples (9b478ad)

---

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]

🧪 Testing

To try out this version of the SDK, run:

pip install 'https://pkg.stainless.com/s/arcade-engine-python/fa2198fb612c3704321bedf76744faa6847e3f52/arcadepy-1.10.0-py3-none-any.whl'

Expires at: Thu, 05 Mar 2026 18:05:24 GMT
Updated at: Tue, 03 Feb 2026 18:05:24 GMT

[byrro]

Would it be possible to name this method create_or_update? Only create may give the impression that it would fail if the secret already exists, which won't be the behavior. Although the docstring says "Create or update", I think the method name is important to communicate the expected behavior as well.

[EricGustin]

yup upsert or create_or_update would make much more sense than create. I took a look at the Engine code and it calls this upsert, so I'm not really sure why stainless is generating this as create.