chore: upgrade postgresql to 42.7.10 due to CVE#4420
Draft
pjfanning wants to merge 2 commits intoapache:mainfrom
Draft
chore: upgrade postgresql to 42.7.10 due to CVE#4420pjfanning wants to merge 2 commits intoapache:mainfrom
pjfanning wants to merge 2 commits intoapache:mainfrom
Conversation
pjfanning
changed the title
github-actions
Bot
added
engine
dependencies
Signed-off-by: Xinyuan Lin <[email protected]>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 changes were proposed in this PR?
CVE-2025-49146 affects 42.7.4 which is used in various places
Any related issues, documentation, discussions?
How was this PR tested?
Was this PR authored or co-authored using generative AI tooling?