Release 3.23.0

[rsareddy0329]

Issue #, if available:

Description of changes:
Standard minor release cut from master at 60857c14, bumping all five packages to their .23.0 versions. This PR contains only the release mechanics - VERSION bumps, internal dependency-pin updates, and CHANGELOG entries. No functional code changes.

Package versions

Package	From	To
sagemaker (meta)	3.22.1	3.23.0
sagemaker-core	2.22.1	2.23.0
sagemaker-train	1.22.1	1.23.0
sagemaker-serve	1.22.1	1.23.0
sagemaker-mlops	1.22.1	1.23.0

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 @rsareddy0329's task in 30s —— View job

---

Release PR Review — 3.23.0

• Read the PR diff (/tmp/pr.diff)
• Verify version bumps are consistent across all packages
• Cross-check dependency pins
• Cross-check CHANGELOG entries

Summary

This is a mechanical release PR — VERSION bumps, internal dependency-pin updates, and CHANGELOG entries only. No functional code changes. It looks clean and internally consistent. ✅

Version bumps (all consistent with the PR description):

Package	From → To
sagemaker (meta)	3.22.1 → 3.23.0
sagemaker-core	2.22.1 → 2.23.0
sagemaker-train	1.22.1 → 1.23.0
sagemaker-serve	1.22.1 → 1.23.0
sagemaker-mlops	1.22.1 → 1.23.0

Dependency pins — updated consistently and correctly:

• Root pyproject.toml: all four sub-packages bumped to their .23.0 lower bounds, upper bounds preserved (<3.0.0 / <2.0.0).
• sagemaker-mlops → core>=2.23.0, train>=1.23.0, serve>=1.23.0 ✓
• sagemaker-serve → core>=2.23.0, train>=1.23.0 ✓
• sagemaker-train → core>=2.23.0 ✓

CHANGELOG consistency — the per-package entries roll up cleanly into the root CHANGELOG.md. Every PR referenced in a sub-package changelog (#6224, #6286, #6293, #6301, #6256, #6204, #6290, #6281, #6306, #6308, #6304, #6300, #6272, #6294) also appears in the aggregate root entry, and vice versa. Dates are consistent (2026-09-24).

Observations (non-blocking)

• The sub-package pyproject.toml files pin internal deps with a lower bound only (e.g. sagemaker-core>=2.23.0), whereas the root meta package uses bounded pins (>=2.23.0,<3.0.0). This asymmetry is pre-existing (not introduced by this PR), but worth a note: without upper bounds, a future sagemaker-core 3.x could satisfy the sub-package constraints. Not a release-blocker.

No correctness, security, or test concerns — release mechanics only, and nothing here changes runtime behavior. Since the PR is already merged, no changes are needed.