Repository navigation
Daily Sync with Botocore v1.43.114 on 2026/10/16 - #6492
sagemaker-bot wants to merge 1 commit into
Conversation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
🤖 AI code review
Automated daily botocore sync (v1.43.114) regenerating service-2.json samples, resources.py, shapes.py, shape_dag.py, and config_schema.py. Changes are overwhelmingly additive (new pipeline step metadata shapes: Athena/Cleanup/EMRServerless/ForEach/IterationContext; new runtime headers PrefixAwareId, S3OutputPathExtension, Filename, inline async Body) plus large documentation churn ("SageMaker" → "SageMaker AI"). Cross-file wiring is consistent and the relocated ConflictException has no duplicate. Two notable items: a recurring source-breaking reorder of Endpoint.invoke_async, and incidental module-docstring deletions in two generated files.
Reviewed commit d972707. Automated review; verify before acting.
| def invoke_async( | ||
| self, | ||
| input_location: StrPipeVar, | ||
| content_type: Optional[StrPipeVar] = Unassigned(), |
There was a problem hiding this comment.
🟠 Medium: invoke_async's signature is reordered so that input_location moves from a required first positional parameter to an optional keyword (content_type is now first positional). This is backward-incompatible for any caller that passes input_location positionally — endpoint.invoke_async("s3://...") will now bind the S3 URI to content_type. This mirrors the upstream API change (Body and InputLocation are mutually exclusive), but as with prior syncs it should be called out in the release notes as a breaking change for positional callers. Source: #6365
| @@ -1,5 +1,3 @@ | |||
| """JSON schema definition for the SageMaker Python SDK configuration file.""" | |||
|
|
|||
| SAGEMAKER_PYTHON_SDK_CONFIG_SCHEMA = { | |||
There was a problem hiding this comment.
🟡 Low: The module docstring ("""JSON schema definition for the SageMaker Python SDK configuration file.""") was dropped by this sync. The same deletion occurs in shape_dag.py. These look like incidental generator churn rather than an intended change; worth confirming the code generator template didn't regress, since typical botocore syncs are purely additive and don't remove existing module docstrings.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #6492 +/- ##
===========================================
+ Coverage 57.31% 73.02% +15.70%
===========================================
Files 571 571
Lines 71735 71771 +36
===========================================
+ Hits 41117 52409 +11292
+ Misses 30618 19362 -11256 🚀 New features to boost your workflow:
|
This branch was successfully deployed
1 participant
Daily sync with Botocore package. This PR is automatically generated by sagemaker-bot.