fix: pin working version for cdk-constructs breaking change#389
Open
fix: pin working version for cdk-constructs breaking change#389
Conversation
noah-paige
previously approved these changes
Jan 13, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Describe your changes
This is short term fix for the bug reported here #388
The
@cdklabs/generative-ai-cdk-constructslibrary introduced an undocumented breaking change in version 0.1.312 that affects how SageMaker deployment constructs are exported. Prior to this version, the library used "barrel exports" (export * from) which allowed consumers to import classes likeJumpStartModel,SageMakerInstanceType, andJumpStartSageMakerEndpointdirectly from the package root. In version 0.1.312, these exports were changed to "namespaced exports" (export * as sagemaker_deployment from), which means the classes are now only accessible under the sagemaker_deployment namespace.This change breaks the sagemaker-jumpstart-fm-endpoint module, which uses the direct import pattern. As a temporary workaround, the module has been pinned to version 0.1.311, which still supports direct imports. The sagemaker-hugging-face-endpoint module is also affected but currently works because its lockfile pins an older version (0.1.74). Both modules will eventually need to be migrated to use namespaced imports (import { sagemaker_deployment } from "@cdklabs/generative-ai-cdk-constructs") and then destructure the required classes, allowing them to upgrade to the latest library version and receive future updates.
New package-lock will also fix an issue with a version bump from a previous pull request.
Version Comparison (to show the change):
Issue ticket number and link
Checklist before requesting a review
CHANGELOG.MDwith a description of my changesscripts/validate.sh)seedfarmer applyBy submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.