Dummy commit to trigger a new container image build for fixing vulnerabilities #19
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
mahithsuresh
changed the title
aws-patlin
approved these changes
Nov 25, 2020
ycnie
approved these changes
Nov 25, 2020
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.
The SparkML-Serving-Container:2.4 contains a bunch of vulnerabilities which is blocking some customers from being able to use it. In order to resolve these, the container image needs to be rebuilt. In order to rebuild the image, I am creating a dummy commit by just adding to the change log.
However, we released SparkML-Serving-Container:2.4 a couple of months back but I realized that we never updated the ChangeLog. So I thought I'll update that.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.