chore: upgrade postgresql to 42.7.10 due to CVE#4420
Conversation
|
@aglinxinyuan @bobbai00 do we need this in for 1.1? |
It's not required, but we can still proceed with the upgrade. We can merge it after merging those test PRs, such that the testing will be easier. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4420 +/- ##
=========================================
Coverage 42.22% 42.23%
Complexity 2180 2180
=========================================
Files 980 980
Lines 36287 36287
Branches 3783 3783
=========================================
+ Hits 15321 15324 +3
+ Misses 20037 20036 -1
+ Partials 929 927 -2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Closing. There is an issue that needs investigation and I think I'll need to leave it to the Texera team to do this. https://github.com/apache/texera/actions/runs/25405045722/job/74514056705 |
d632519 to
a4a1987
Compare
|
ok - this set of changes seems to be getting further in the build |
bobbai00
left a comment
There was a problem hiding this comment.
LGTM! Thank you very much for this effort @pjfanning
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?