fix(sec): upgrade org.postgresql:postgresql to 42.4.1 #1616
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
leonardBang
approved these changes
Oct 18, 2022
leonardBang
pushed a commit
to lxxawfl/flink-cdc-connectors
that referenced
this pull request
Oct 18, 2022
leonardBang
added a commit
to lxxawfl/flink-cdc-connectors
that referenced
this pull request
Oct 18, 2022
leonardBang
force-pushed
the
oscs_fix_cd4jcloau51t5k2gfh8g
branch
from
661a834
to
7dc17bb
Compare
leonardBang
force-pushed
the
oscs_fix_cd4jcloau51t5k2gfh8g
branch
from
7dc17bb
to
f4d2226
Compare
leonardBang
pushed a commit
that referenced
this pull request
Oct 18, 2022
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 happened？
There are 1 security vulnerabilities found in org.postgresql:postgresql 42.3.1
What did I do？
Upgrade org.postgresql:postgresql from 42.3.1 to 42.4.1 for vulnerability fix
What did you expect to happen？
Ideally, no insecure libs should be used.
How was this patch tested?
Run
mvn compilefailed locally, couldn't complete the build process.Run
mvn clean testfailed locally, unit-test couldn't pass.The specification of the pull request
PR Specification from OSCS