fix(test): upgrade assertj-core to 3.27.7 to address vulnerability#355
Merged
pwgit-create merged 1 commit intodevelopfrom Feb 1, 2026
Merged
fix(test): upgrade assertj-core to 3.27.7 to address vulnerability#355pwgit-create merged 1 commit intodevelopfrom
pwgit-create merged 1 commit intodevelopfrom
Conversation
Closed
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
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.
🛡️ Security Fix: Upgrade AssertJ to Safe Version
What’s changed
This PR addresses a reported security vulnerability by upgrading AssertJ used in test scope:
org.assertj:assertj-coreThe upgrade is applied via dependency management to ensure the safe version is consistently used across the test classpath.
Why
assertj-core:3.27.6is flagged with a known vulnerability3.27.7contains the upstream fixVerification
mvn dependency:treethat onlyassertj-core:3.27.7is resolvedRisk
🟢 Low — version bump within the same minor release, test-only dependency.
The assertj-bom:3.25.3 download you see is normal — Maven sometimes pulls BOM metadata, but your actual resolved artifact is still assertj-core:3.27.7