fix: fixed a security alert by updating brace-expansion#156
Merged
jkalandaibm merged 1 commit intomasterfrom Jun 23, 2025
Merged
fix: fixed a security alert by updating brace-expansion#156jkalandaibm merged 1 commit intomasterfrom
jkalandaibm merged 1 commit intomasterfrom
Conversation
dependency: none Signed-off-by: jkalanda <jkalanda@us.ibm.com>
jkalandaibm
force-pushed
the
update-brace-expansion
branch
from
83b36f5 to
191df18
Compare
kennburger
approved these changes
Jun 23, 2025
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.
dependency: none
PR summary
The Issue is addressing the following vulnerability
https://github.com/IBM/networking-java-sdk/security/dependabot/24
Fixes: package brace-expansion was identified to have a vulnerability. A new patched version was released addressing the very vulnerability, consequently I'm updating the version 2.0.2
PR Checklist
Please make sure that your PR fulfills the following requirements:
PR Type
What is the current behavior?
Behavior wasn't altered
What is the new behavior?
Behavior wasn't altered
Does this PR introduce a breaking change?
Other information