Add sagemaker dependency for remote function by default V3 #5487
+681
−13
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
aviruthen
temporarily deployed
to
auto-approve
GitHub Actions
Inactive
mollyheamazon
approved these changes
Jan 16, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #, if available:
Description of changes:
Resolving an issue where integrity checks change across sagemaker 3.1.0- and sagemaker 3.2.0+. Standardizing checks in local and remote environment by ensuring that when users use sagemaker 3.2.0+, they are installing sagemaker 3.2.0 or greater in their remote environments by default
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.