-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Upgrading OSS libraries with known open CVEs #3778
Upgrading OSS libraries with known open CVEs #3778
Conversation
+1 |
Need this as well. |
+1 |
@scottcarter87 can you take a look at the failing build? |
@v1r3n I get the same error locally. Taking a look. |
Still getting a weird error locally on java-sdk for one test. Not sure if its my local setup (M2 Mac) which also has issues with the version of test containers used or if there is an additional test issue now. The first CI failure was resolved by using a newer protobuf version. WorkflowCreationTests.verifyInlineWorkflowExecution()
|
@v1r3n All of the build issues have been resolved and I get a clean build locally. Please run the build again if you could. |
Added to the main description |
What is left to do in order to apply the improvement? |
+1 |
Updated with the latest code from main |
@v1r3n any specific reason this is still sitting un-merged? |
Pull Request type
./gradlew generateLock saveLock
to refresh dependencies)NOTE: Please remember to run
./gradlew spotlessApply
to fix any format violations.Changes in this PR
Upgrading OSS libraries used within conductor that have known CVEs. The vulnerable packages were detected by our OSSPI container scans and needed to be fixed in order for us to remain compliant and able to use conductor. This PR applies the fixes that we needed to ensure that Conductor could be deployed within our environment.