release: 3.29.0

[stainless-app]

Automated Release PR

3.29.0 (2026-03-12)

Full Changelog: v3.28.0...v3.29.0

Features

• api: api update (fe80425)
• api: api update (de304ee)

---

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:

pip install 'https://pkg.stainless.com/s/supermemory-new-python/fe80425181b93862c2d544b5d5664827aa41a57a/supermemory-3.28.0-py3-none-any.whl'

Expires at: Sat, 11 Apr 2026 20:23:14 GMT
Updated at: Thu, 12 Mar 2026 20:23:14 GMT

[sentry]

Bug: The delete_documents parameter is incorrectly typed as str instead of bool. This contradicts its documented behavior and will cause type-checking and serialization errors.
_{Severity: MEDIUM}

Suggested Fix

Change the type annotation for the delete_documents parameter from str to bool in connection_delete_by_id_params.py and any related function signatures, such as in connections.py. The type should be Annotated[bool, PropertyInfo(alias="deleteDocuments")].

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: src/supermemory/types/connection_delete_by_id_params.py#L13

Potential issue: The `delete_documents` parameter in `connection_delete_by_id_params.py`
is typed as `str`, but its docstring ("Whether to also delete documents... Defaults to
true.") and intended function indicate it should be a boolean. This incorrect type hint
will cause type checkers to flag correct usage (passing `True` or `False`) as an error.
Furthermore, if a user passes a Python boolean, the SDK's serialization may produce an
incorrect value (e.g., `"True"` instead of the expected `"true"`), leading to API
failures. This is inconsistent with other boolean parameters in the codebase, such as
`include_content`.

_{Did we get this right? 👍 / 👎 to inform future reviews.}