Repository navigation
release(clients): caura-client 1.1.1 for Python and TypeScript - #2117
Merged
Merged
Conversation
Bumps both SDK clients to 1.1.1 so the next publish carries #2116, the only client change since the 1.1.0 tags (caura-client-v1.1.0 and caura-client-ts-v1.1.0 at fd1da78): - stats() rejects a 2xx body that is not JSON, or not a JSON object, with CauraAPIError / CauraApiError, as the other methods do (L-237). - RateLimitError.retry_after is None/null unless the delay is finite and non-negative (L-238). Patch: fixes only, no API change. Versions only: pyproject.toml and _version.py; package.json, package-lock.json (its own two entries) and src/version.ts. Signed-off-by: eldad-caura <eldad@caura.ai> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
Claude Code Review ✅ No issues found. Reviewed by |
Member
Author
|
@erni-a please review |
erni-a
approved these changes
Oct 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Bumps both SDK clients to 1.1.1 so the next publish carries #2116, the only client change since 1.1.0. The 1.1.0 tags are
caura-client-v1.1.0andcaura-client-ts-v1.1.0at fd1da78.Versions only:
clients/python/pyproject.tomlandcaura_client/_version.py.clients/typescript/package.json,package-lock.json(its own two entries) andsrc/version.ts.What 1.1.1 carries
#2116, in both clients:
stats()rejects a 2xx body that is not JSON, or not a JSON object, withCauraAPIError/CauraApiError, assearch()andrecall()do. Before, Python leakedJSONDecodeErrororAttributeError, and TypeScript returned zero counters.RateLimitError.retry_afterisNone/nullunless the delay is finite and non-negative. Before, Python passed throughnan,infand negatives, and TypeScript passed negatives and read a blank header as 0.Why a patch: fixes only, with no new API. A caller only sees a difference for a malformed response or header.
Release, after merge
Each tag runs its publish workflow, which checks that the tag's version matches the package:
caura-client-v1.1.1→publish-python-client.yml(PyPIcaura-client)caura-client-ts-v1.1.1→publish-npm-client.yml(npm@caura/client)The wrapper packages depend on
caura-client>=1.0.0(caura,caura-sdk),caura-client>=1.0.3(the memclaw shim) and@caura/client ^1.0.0/^1.0.1(npm), so they pick up 1.1.1 without a release of their own.Test plan
__version__agrees withpyproject.toml), and the TypeScript client's build and tests, pass🤖 Generated with Claude Code