-
Notifications
You must be signed in to change notification settings - Fork 38
fix: trying to fix CVE-2025-24970 #367
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
dalelane
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
verified locally - looks good
|
commit message isn't compliant, but I can fix that when I merge I'll wait for the build & test check to pass before I do that |
|
build failure - almost certainly unrelated to the specific change in the PR |
|
|
|
@ghostroot007 Please verify that the app builds correctly with that change by running it, and checking that the fonts are correctly rendered in the browser |
Bumped Vert.x version to the latest stable. Closes: #1234 Signed-off-by: ghostroot007 <[email protected]>
Bumped Vert.x version to the latest stable. Closes: #1234 Signed-off-by: ghostroot007 <[email protected]>
|
Yeah looks good... can you also verify that the fonts are rendered properly in the browser by running the starter application ? |
|
|
|
Yes, I’ve reverted the unintended changes to those files. I ran |
@aswinayyolath I've verified this locally after excluding the WOFF binaries from filtering, and I didn't observe any UI breakages.
|
|
Yeah looks good |






Status
READY
Commit Message
Bumped vertx version to the latest stable release in pom.xml to address High severity vulnerability CVE-2025-24970
Commit Message Description
squash and mergefrom this page.Checklist