build: upgrade dependencies #870
Merged
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
masontikhonov
force-pushed
the
CR-25970--security-fix-critical-and-high-in-codefresh-cli
branch
from
90ca146 to
8e9dd96
Compare
yaroslav-codefresh
approved these changes
Nov 26, 2024
masontikhonov
deleted the
CR-25970--security-fix-critical-and-high-in-codefresh-cli
branch
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
This PR reapplies #866 that was previously reverted in #869.
It contains upgrade for multiple dependencies to address critical- and high-level CVE.
In addition to #866, it:
npmto address CVE-2024-21538.NODE_NO_WARNINGS=1env in Dockerfile (ref) in order to suppress Node.js deprecation warnings, that may interrupt end-user automations, that rely on exact CLi output.pkg, which is no longer maintained, to its fork@yao-pkg/pkg.