vdk-jupyter: fix build by pinning every package to a specific version #2186
Conversation
This file contains 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
for more information, see https://pre-commit.ci
yonitoo
approved these changes
Jun 8, 2023
DeltaMichael
approved these changes
Jun 8, 2023
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.
What:
Pinned all the dependencies to a specific version and add package-lock.json file. The purpose is to lock the installed dependencies to a specific version number so that subsequent installations can replicate the exact same dependency tree in the future, regardless of any new package releases.
Why:
Because jupyterlab 4 is released some days ago, and it bumps most of the packages to the newest versions which do not seem to be working well for now and been causing some build problems.
Signed-off-by: Duygu Hasan [email protected]