yarn.lock file isn't required by runtime #2024
Conversation
Signed-off-by: Roland.Ma <rolandma@yunify.com>
ks-ci-bot
added
kind/cleanup
|
/assign @harrisonliu5 |
|
/cherrypick release-3.1 |
|
@RolandMa1986: once the present PR merges, I will cherry-pick it on top of release-3.1 in a new PR and assign it to you. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: harrisonliu5, RolandMa1986 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
ks-ci-bot
added
the
approved
|
@RolandMa1986: new pull request created: #2026 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Signed-off-by: Roland.Ma rolandma@yunify.com
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Remove yarn.lock file from the docker image.
There are some false positive CVE issues were reported by the scaner, which try to detect issues with the yarn.lock file. But some of those packages were not compiled into the release.
Which issue(s) this PR fixes:
Fixes #