Release 3.20.0

[zhaoqizqwang]

Issue #, if available:

Description of changes:

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[github-actions]

Claude finished @zhaoqizqwang's task in 34s —— View job

---

Release 3.20.0 — Review

• Read the PR diff (/tmp/pr.diff)
• Verify version bumps are consistent across packages
• Verify dependency constraints match new versions
• Cross-check changelog entries

Findings

This is a mechanical release PR (76 additions / 15 deletions across VERSION, pyproject.toml, and CHANGELOG files). Everything is internally consistent — looks clean, no blocking issues.

Version bumps (all minor, coherent):

Package	Old → New
root sagemaker	3.19.0 → 3.20.0
sagemaker-core	2.19.0 → 2.20.0
sagemaker-train	1.19.0 → 1.20.0
sagemaker-serve	1.19.0 → 1.20.0
sagemaker-mlops	1.19.0 → 1.20.0

Dependency constraints — updated in lockstep with the bumps. Root keeps the >=X,<next-major bounds; the sub-package pyproject.tomls use >= floors. All floors moved to the new minors (e.g. sagemaker-core>=2.20.0), so nothing pins to a version that doesn't exist. ✅

Changelog cross-check — the root CHANGELOG.md aggregates the entries and each per-package changelog carries its own subset. Consistency spot-checks:

• fix(core): propagate user-supplied tags... (#6167) → root + sagemaker-core ✅
• fix(mlops): ...role permissions (#6162) → root + sagemaker-mlops ✅
• feat(serve) (#6148), fix(serve) (#6160), test(serve) (#6141) → root + sagemaker-serve ✅
• fix(train) (#6181), test(train) (#6183, #6180) → root + sagemaker-train ✅

All PRs listed in per-package changelogs appear in the root, and vice versa. Dates (2026-08-14) are uniform.

Minor notes (non-blocking, optional)

• sagemaker-serve/VERSION, sagemaker-mlops/VERSION, and sagemaker-train/VERSION share the same blob SHA (3989355915) simply because they all now contain 1.20.0 — expected, not an issue.
• The sagemaker-mlops changelog for v1.20.0 does not bump sagemaker-serve's floor in its own body text, but its pyproject.toml does move sagemaker-serve>=1.20.0 — consistent. Just flagging that mlops depends on serve/train/core all at the new minors, which is correct.

No correctness, security, or test-coverage concerns for a release PR of this nature.