Remove legacy sauce_junit to eliminate JUnit 4.12 CVE #196
Conversation
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
- pom.xml: drop unused com.saucelabs:sauce_junit (which pulled junit:junit:4.12); keep saucerest and modern JUnit Jupiter + cucumber-junit (junit 4.13.2 patched) - SECURITY.md: add note under Code Quality Security explaining removal of sauce_junit and reliance on patched cucumber-junit bridge Co-authored-by: Cursor <cursoragent@cursor.com>
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.
Summary
Remove the unused legacy Sauce Labs JUnit 4 helper that was pulling in , and document how the JUnit 4 advisory is mitigated.
Changes
Risk
Low. was not referenced in the test code; Sauce Labs integration uses directly. Removing it only shrinks the dependency graph and resolves the JUnit 4.12 advisory.
Made with Cursor