Skip to content

[Snyk] Upgrade junit:junit from 4.13.1 to 4.13.2#5

Open
samuelrizerio wants to merge 1 commit into
mainfrom
snyk-upgrade-0de234555e746dc803fda1eba6830d57
Open

[Snyk] Upgrade junit:junit from 4.13.1 to 4.13.2#5
samuelrizerio wants to merge 1 commit into
mainfrom
snyk-upgrade-0de234555e746dc803fda1eba6830d57

Conversation

@samuelrizerio

@samuelrizerio samuelrizerio commented Nov 14, 2025

Copy link
Copy Markdown
Owner

snyk-top-banner

Snyk has created this PR to upgrade junit:junit from 4.13.1 to 4.13.2.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 1 version ahead of your current version.

  • The recommended version was released 5 years ago.


Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:


Note

Upgrades JUnit to 4.13.2 and standardizes empty XML elements across pom.xml and plugin/profile configurations.

  • Build/Dependencies:
    • Update version.junit from 4.13.1 to 4.13.2 in pom.xml.
  • Build/POM formatting:
    • Normalize empty XML elements to self-closing form across pom.xml (properties, plugin configurations, enforcer rules, m2e lifecycle mappings, Asciidoctor attributes, JaCoCo Ant report tasks, and profiles).

Written by Cursor Bugbot for commit 91137e1. This will update automatically on new commits. Configure here.

Snyk has created this PR to upgrade junit:junit from 4.13.1 to 4.13.2.

See this package in maven:
junit:junit

See this project in Snyk:
https://app.snyk.io/org/samuelrizerio/project/365d35ae-a852-4d90-80c9-b4d803ee80b6?utm_source=github&utm_medium=referral&page=upgrade-pr
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants