Merged
Conversation
68cd348 to
29363bf
Compare
2ab59a2 to
754d6f1
Compare
0f1f5f3 to
f8f9943
Compare
danielmillerp
approved these changes
Apr 14, 2026
Contributor
Author
|
🤖 Release is at https://github.com/scaleapi/scale-agentex-python/releases/tag/v0.10.0 🌻 |
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.10.0 (2026-04-14)
Full Changelog: v0.9.10...v0.10.0
Features
Bug Fixes
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 the automated 0.10.0 release PR, bumping the version across
pyproject.toml,_version.py, and the release manifest. The substantive code changes are a targeted bug fix in_extract_items(ensuring top-level file-array fields are properly removed from the request body) and a newproduction_deployment_idfield on theAgentmodel.Confidence Score: 5/5
_extract_itemsis correct: replacing the index-based pop condition with theall(p == "<array>" ...)check properly handles top-level file arrays while preserving existing behaviour for all other path shapes. The vacuously-true empty-slice case correctly handles leaf-node removal. The new test directly exercises the previously broken path.Important Files Changed
len(path) == indextoall(p == "<array>" for p in path[index:]), correctly removing a dict key when only array-traversal markers remain in the path (fixes top-level file-array fields not being stripped from the request body).test_top_level_file_arraythat directly covers the fixed bug: verifies that files at a top-level array path are extracted and the source key is removed from the query dict.production_deployment_id: Optional[str]field to theAgentmodel, following the ID-reference pattern used throughout the codebase.Flowchart
%%{init: {'theme': 'neutral'}}%% flowchart TD A[_extract_items called with path and index] --> B[key = path at index] B --> C[increment index] C --> D{obj is dict?} D -- Yes --> E{remaining path is only array markers?} E -- True --> F[pop key from obj - removes from body] E -- False --> G[access obj key - keeps in body, traverse deeper] F --> H[recurse with extracted item] G --> H D -- No --> I{obj is list?} I -- Yes --> J{key is array marker?} J -- Yes --> K[iterate list, recurse each element] J -- No --> L[return empty] H --> M[path exhausted - return file tuples] K --> MReviews (34): Last reviewed commit: "release: 0.10.0" | Re-trigger Greptile