release: 2.7.0 - #245
Open
stainless-app[bot] wants to merge 13 commits into
Open
Conversation
Contributor
Author
|
🧪 Testing To try out this version of the SDK: Expires at: Thu, 27 Aug 2026 23:23:48 GMT |
…t in workflow templates
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
July 17, 2026 17:20
d9feaff to
c78e59f
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
July 17, 2026 17:21
c78e59f to
eed8564
Compare
…50cc737f03437 Picks up ComputeAttribute support (turbopuffer/turbopuffer-apigen).
…-attributes scripts: bump turbopuffer-apigen image for ComputeAttribute support
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
July 17, 2026 23:34
eed8564 to
54f11a3
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
July 18, 2026 00:06
54f11a3 to
688106a
Compare
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
July 24, 2026 15:41
688106a to
6aef733
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
July 24, 2026 18:00
6aef733 to
dbe1c32
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
July 24, 2026 19:58
dbe1c32 to
5efa7a9
Compare
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 5efa7a9. Configure here.
| [[package]] | ||
| name = "turbopuffer" | ||
| version = "2.4.0" | ||
| version = "2.6.0" |
There was a problem hiding this comment.
Lockfile version lags release
Low Severity
The root turbopuffer entry in uv.lock is 2.6.0 while this release sets 2.7.0 in pyproject.toml, _version.py, and the release-please manifest. The lock was updated in this change set but not to the released version.
Reviewed by Cursor Bugbot for commit 5efa7a9. Configure here.
Lands the apigen-generated ComputeAttributes union into custom.py. The auto regen workflow can't push to next (ruleset requires a PR), so landing via PR. Depends on the HighlightConfig->HighlightConfigParams rename (now on next). Verified: ruff format leaves it unchanged (idempotent), syntax valid.
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
July 27, 2026 21:57
5efa7a9 to
4b86ab5
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
July 27, 2026 23:33
4b86ab5 to
6a04390
Compare
…tes` (#247) * Rich compute_attributes typing (Path B override) Hand-type the compute_attributes query param as Dict[str, ComputeAttributes] using the apigen union in custom.py, across namespace_query_params, namespace_explain_query_params, and namespace_multi_query_params. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * chore: regenerate custom.py (ComputeAttributesVectorDist -> Sequence[float]) The committed custom.py carried a stale ComputeAttributesVectorDist using Vector; current apigen emits Sequence[float] (per the inline VectorDist spec change). Regenerated via scripts/gen so 'supplemental generated code' is current. * test: use valid ComputeAttributes union values in namespace tests compute_attributes is now Dict[str, ComputeAttributes], so the generated {"foo": "bar"} mocks no longer typecheck. Use the Highlight tuple ("Highlight", "bar"), mirroring how aggregate_by uses ("Sum", "bar"). * test: add ComputeAttributes union serialization test Exercises every variant of the ComputeAttributes union (VectorDist, Highlight, HighlightWithConfig, RankBy) through the request-body serialization path (maybe_transform over NamespaceQueryParams) and asserts the JSON wire form for each. Placed in a non-skipped module so it runs in CI (the generated api_resources tests and test_transform.py are skipped). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
July 28, 2026 17:56
6a04390 to
5f13a9c
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
July 28, 2026 23:23
5f13a9c to
21510ad
Compare
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
2 participants
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.
Automated Release PR
2.7.0 (2026-07-28)
Full Changelog: v2.6.0...v2.7.0
Features
Bug Fixes
Chores
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