release: 0.11.4#364
Open
stainless-app[bot] wants to merge 2 commits into
Open
Conversation
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.
Automated Release PR
0.11.4 (2026-05-22)
Full Changelog: v0.11.3...v0.11.4
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
Greptile Summary
This is an automated release PR bumping the SDK version from 0.11.3 to 0.11.4. The only substantive change is relaxing the
redisdependency pin from>=5.2.0,<6to>=5.2.0,<8, allowing the library to work with redis-py 6.x and 7.x clients.pyproject.toml,.release-please-manifest.json, andsrc/agentex/_version.py.<6to<8; the resolved lock files pin toredis==7.4.0, a jump of two major versions (5.3.1 → 7.4.0). Between redis-py 5 and 7 several APIs changed (e.g. thePyJWTdependency was dropped, connection URL defaults shifted) — worth a smoke-test if any internal code reaches advanced redis features.pydantic-ai-slim==1.101.0andpydantic-graph==1.101.0appearing for the first time as resolved packages; both are already declared as direct dependencies inpyproject.toml(pydantic-ai-slim>=1.0,<2) so this is expected lock-file materialisation, not a new addition.Confidence Score: 5/5
Safe to merge — straightforward automated release bump with one dependency ceiling change.
All version strings are in sync across the four files that carry them. The only functional change is lifting the redis upper bound from <6 to <8; the lock files resolve cleanly to redis 7.4.0 and all transitive dependency changes (pydantic-ai-slim materialising, pyjwt dropped from redis) are expected consequences of that upgrade.
No files require special attention; lock file changes are generated and the pyproject.toml delta is minimal.
Important Files Changed
Flowchart
%%{init: {'theme': 'neutral'}}%% flowchart TD A[pyproject.toml\nredis >=5.2.0,<8] --> B{Lock file resolution} B --> C[redis==7.4.0\nup from 5.3.1] B --> D[pydantic-ai-slim==1.101.0\nalready declared, now resolved] B --> E[pyjwt no longer\na redis transitive dep] C --> F[requirements.lock\nrequirements-dev.lock] D --> F E --> F F --> G[Version bump\n0.11.3 to 0.11.4] G --> H[pyproject.toml\n_version.py\n.release-please-manifest.json\nCHANGELOG.md]Reviews (1): Last reviewed commit: "release: 0.11.4" | Re-trigger Greptile