Skip to content

feat: update SDK to use latest LMI v30 image for sdk v2.x - #6484

Merged
rsareddy0329 merged 1 commit into
aws:master-v2from
ethnzhng:v30-2x
Oct 29, 2026
Merged

rsareddy0329 merged 1 commit into
aws:master-v2from
ethnzhng:v30-2x

Conversation

@ethnzhng

Copy link
Copy Markdown

Summary

Updates the DJL-LMI image config to the newly released LMI v30 (0.38.0-lmi30.0.0-cu130, DJL Serving 0.38.0 / vLLM 0.31.0) for SageMaker Python SDK 2.x (master-v2). DJL Serving stays at 0.38.0, so this edits the 0.38.0 key in place and the registries map is unchanged.

Changes

  • src/sagemaker/image_uri_config/djl-lmi.json: bump the 0.38.0 tag_prefix from 0.38.0-lmi29.0.0-cu130 to 0.38.0-lmi30.0.0-cu130
  • tests/unit/sagemaker/image_uris/test_djl.py: register 0.38.0-lmi30.0.0-cu130 in KNOWN_MISSING_COMBINATIONS (ap-east-2). The 2.x 0.38.0 registries have no ap-east-2 entry, so test_djl_lmi_config_for_framework_has_all_regions[djl-lmi] fails without it.

Testing

  • pytest tests/unit/sagemaker/image_uris/test_djl.py: 8 passed on Python 3.9 and 3.11
  • image_uris.retrieve("djl-lmi", region="us-west-2", version="0.38.0") and version="latest" both return 763104351884.dkr.ecr.us-west-2.amazonaws.com/djl-inference:0.38.0-lmi30.0.0-cu130; the 0.36.0 key still returns the lmi27 tag

Note

2.x SM-PY-SDK release requires PM/TPM approval before merge.

Bump the 0.38.0 tag_prefix in djl-lmi.json from 0.38.0-lmi29.0.0-cu130
to 0.38.0-lmi30.0.0-cu130, and register the new tag in
KNOWN_MISSING_COMBINATIONS (ap-east-2) as for earlier LMI releases.

DJL Serving stays at 0.38.0, so the existing key is edited in place.
The registries map and version_aliases are unchanged.
@rsareddy0329
rsareddy0329 merged commit b38c4d0 into aws:master-v2 Oct 29, 2026
9 of 11 checks passed
@ethnzhng
ethnzhng deleted the v30-2x branch October 29, 2026 16:54

This branch was successfully deployed

1 active deployment
manual-approval — da02b6aa Deployed Oct 15, 2026 by ethnzhng via wait-for-approval #257
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants