Daily Sync with Botocore v1.43.87 on 2026/09/02

[sagemaker-bot]

Daily sync with Botocore package. This PR is automatically generated by sagemaker-bot.

[github-actions]

Claude finished @sagemaker-bot's task in 1m 12s —— View job

---

Claude review — Daily Botocore sync (v1.43.87)

• Read the PR diff (/tmp/pr.diff)
• Analyze the generated Python changes (resources.py, shapes.py, shape_dag.py, config_schema.py)
• Check for backward-incompatibility and in-repo callers
• Post review

---

This is an auto-generated botocore model sync. The bulk is additive: new shapes (LoRA AIAdapterSource, AIMlflowConfig, ContainerMetricsConfig, PrefixAwareRoutingConfig, IdcConfig*, Job, MetricsEndpoint*, ClusterAutoPatchConfig*), new enum values (RoutingStrategy.PREFIX_AWARE, StorageType.Standard_V2, PartnerAppAuthType.IDC, NotebookInstanceStatus.PendingMaintenance/InMaintenance, IncludedData), new instance types (ml.g7.*, ml.g6e.*, etc.), and new optional params. These are wired consistently across resources.py, shapes.py, shape_dag.py, and config_schema.py. No obvious generator breakage. No prompt-injection content in the diff.

Two things worth calling out — both stem from upstream model changes, not hand edits, so no fix is expected in this automated PR:

1. Endpoint.invoke_async — potential positional-arg breaking change (sagemaker-core/src/sagemaker/core/resources.py:10788)

input_location changed from the first required positional parameter to an optional one, and was moved below content_type/accept/custom_attributes/inference_id:

# before
def invoke_async(self, input_location: StrPipeVar, content_type=..., ...)
# after
def invoke_async(self, content_type=..., accept=..., custom_attributes=...,
                 inference_id=..., input_location=Unassigned(), ..., body=Unassigned())

Any external caller invoking positionally (endpoint.invoke_async("s3://…")) would now silently bind that S3 URI to content_type. This mirrors the upstream API (InputLocation is no longer required now that an inline Body is supported and the two are mutually exclusive). In-repo usage is keyword-based (input_location=… in inference_and_resource_chaining.ipynb), so nothing here breaks — flagging only for downstream consumers. Note there is no client-side validation that exactly one of body/input_location is provided, but that also matches the service contract.

2. Minor generated-docstring mismatch (sagemaker-core/src/sagemaker/core/shapes/shapes.py:2200)

The new ConflictException docstring reads "There was a conflict when you attempted to modify a SageMaker entity such as an Experiment or Artifact.", whereas the featurestore-runtime model documents this exception as an out-of-order EventTime conflict on UpdateRecord. Cosmetic only (comes from a shared/synthetic shape name); no behavioral impact.

No tests are added, which is expected for a generated model sync. Nothing here blocks the merge.
· branch botocore-sync-2026-09-02-19-35-15

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 70.93%. Comparing base (0316c38) to head (d8c95a6).

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #6236      +/-   ##
==========================================
+ Coverage   70.90%   70.93%   +0.03%     
==========================================
  Files         553      553              
  Lines       68029    68113      +84     
==========================================
+ Hits        48233    48317      +84     
  Misses      19796    19796              

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.