Skip to content

Upgrade sm-mlflow_pipeline.ipynb to sagemaker v3#4873

Merged
mollyheamazon merged 1 commit intoaws:defaultfrom
pdifranc:upgrade_mlops_sagemaker_pipeline
Feb 24, 2026
Merged

Upgrade sm-mlflow_pipeline.ipynb to sagemaker v3#4873
mollyheamazon merged 1 commit intoaws:defaultfrom
pdifranc:upgrade_mlops_sagemaker_pipeline

Conversation

@pdifranc
Copy link
Copy Markdown
Contributor

Issue #, if available:

Description of changes:

Upgrade sagemaker python sdk from v2 to v3

Testing done: yes

Merge Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your pull request.

  • I have verified that my PR does not contain any new notebook/s which demonstrate a SageMaker functionality already showcased by another existing notebook in the repository
  • I have read the CONTRIBUTING doc and adhered to the guidelines regarding folder placement, notebook naming convention and example notebook best practices
  • I have updated the necessary documentation, including the README of the appropriate folder as well as the index.rst file
  • I have tested my notebook(s) and ensured it runs end-to-end
  • I have linted my notebook(s) and code using python3 -m black -l 100 {path}/{notebook-name}.ipynb

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@review-notebook-app
Copy link
Copy Markdown

Check out this pull request on  ReviewNB

See visual diffs & provide feedback on Jupyter Notebooks.


Powered by ReviewNB

@pdifranc pdifranc force-pushed the upgrade_mlops_sagemaker_pipeline branch from e36325b to 791cb25 Compare February 17, 2026 21:32
@mollyheamazon mollyheamazon merged commit 58a3cd5 into aws:default Feb 24, 2026
1 check passed
@pdifranc pdifranc deleted the upgrade_mlops_sagemaker_pipeline branch February 24, 2026 19:18
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