release: 1.77.0

[stainless-app]

Automated Release PR

1.77.0 (2026-06-13)

Full Changelog: v1.76.0...v1.77.0

Features

• api: add legal entity simulation endpoint (17744ee)
• api: api update (ffd46a4)
• api: api update (c6954f8)
• api: api update (f09cbb9)
• api: api update (b7cde24)
• api: api update (d2ecccf)
• api: api update (93d5c22)
• api: api update (3e04824)
• api: api update (e642947)
• api: api update (c10be6e)
• api: api update (cee241d)
• api: api update (3854d6b)
• api: api update (f228554)
• api: api update (67b3d97)
• api: api update (252aef7)
• api: api update (fe8aabc)
• api: api update (8f7ab08)
• api: api update (ced4eb1)
• api: api update (ec6cfcf)
• api: api update (1da3c13)
• api: api update (47e5835)
• api: api update (88d127f)
• api: api update (a960ed8)
• internal/types: support eagerly validating pydantic iterators (0de6c33)
• support setting headers via env (12b4a5f)

Bug Fixes

• client: add missing f-string prefix in file type error message (b931d8d)
• use correct field name format for multipart file arrays (c18d9fa)

Chores

• internal: codegen related update (816b839)
• internal: reformat pyproject.toml (0a622b0)

---

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

[devin-ai-integration]

Devin Review found 1 potential issue.

View 2 additional findings in Devin Review.

[devin-ai-integration]

🚩 copy(set_default_headers=...) semantics changed by env header injection

The copy() method at src/modern_treasury/_client.py:521 passes headers to __init__(), which now re-reads MODERN_TREASURY_CUSTOM_HEADERS from the environment at line 204-211. When a user calls copy(set_default_headers={}) intending to clear all custom headers, env-derived headers would still be injected via {**parsed, **default_headers}. This is a semantic change to set_default_headers — previously it would result in zero custom headers, now env headers persist. This is likely intentional (env headers are always-on infrastructure config), but it's worth documenting since it changes the contract of set_default_headers. The same applies to the async client at line 664.

---

Was this helpful? React with 👍 or 👎 to provide feedback.

[devin-ai-integration]

Devin Review found 2 new potential issues.

View 11 additional findings in Devin Review.

[devin-ai-integration]

🚩 LedgerEntryCreateRequest.amount changed from Required to optional

In both src/modern_treasury/types/shared/ledger_entry_create_request.py and src/modern_treasury/types/shared_params/ledger_entry_create_request.py, amount was changed from a required field to optional (Optional[int] = None / non-Required). The new amount_string field is also optional. This means neither amount nor amount_string is required, which could allow creating a ledger entry with no amount specified. This appears to be an intentional API spec change (the server presumably validates that at least one is provided), but callers relying on the type system to enforce amount presence will no longer get that guarantee.

---

Was this helpful? React with 👍 or 👎 to provide feedback.

[devin-ai-integration]

🚩 Currency enum removes USDB and USDP stablecoin values

In both src/modern_treasury/types/shared/currency.py and src/modern_treasury/types/shared_params/currency.py, the USDB and USDP currency values were removed from the Currency type. If any existing API consumers are using these currency values, their code would still work at runtime (the values are just strings sent to the API), but type checkers would flag them. This is a potentially breaking change for users relying on these specific currencies.

---

Was this helpful? React with 👍 or 👎 to provide feedback.

[devin-ai-integration]

Devin Review found 1 new potential issue.

[devin-ai-integration]

🚩 _EagerIterable inherits from list[_T] but is only used as Annotated metadata

The _EagerIterable class inherits from list[_T] and Generic[_T], but is never instantiated directly — it's only used as metadata in Annotated[Iterable[_T], _EagerIterable]. The list inheritance seems unnecessary for its purpose as a pydantic schema marker. However, pydantic v2 does look for __get_pydantic_core_schema__ on metadata classes, and the implementation correctly uses @classmethod and @staticmethod methods. The list[_T] base class requires Python 3.9+ at runtime (since it's a base class, not an annotation, from __future__ import annotations doesn't help). This is presumably acceptable given the project's Python version requirements.

---

Was this helpful? React with 👍 or 👎 to provide feedback.