Bump JunitXml.TestLogger from 6.1.0 to 7.0.1

[dependabot]

Updated JunitXml.TestLogger from 6.1.0 to 7.0.1.

Release notes

Sourced from JunitXml.TestLogger's releases.

7.0.1

7.0.1 (2025-10-04)

Bug Fixes

• prep for 7.0.1 release (#​196) (5cb9d0b)

7.0.0

7.0.0 (2025-09-22)

⚠ BREAKING CHANGES

• MTP integration for spekt loggers

Features

• add support for Microsoft.Testing.Platform (#​172) (b6d9a23)
• MTP integration for spekt loggers (30f586b)

Bug Fixes

• escape suite-level system-out and system-err messages in JUnit logger (#​187) (d8707e9)
• sanitize out and err text in loggers (#​188) (d9f8347)

Commits viewable in compare view.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot will merge this PR once CI passes on it, as requested by @guibranco.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Description by Korbit AI

What change is being made?

Bump the JunitXml.TestLogger package from 6.1.0 to 7.0.1 in Tests/POCDijkstra.Tests/POCDijkstra.Tests.csproj.

Why are these changes being made?

Upgrade to the latest test logger to maintain compatibility with the updated test tooling and improve logging behavior. No additional functional changes were required.

Is this description stale? Ask me to generate a new description by commenting /korbit-generate-pr-description

[semanticdiff-com]

Review changes with  

Changed Files

File	Status
Tests/POCDijkstra.Tests/POCDijkstra.Tests.csproj	40% smaller

[pr-code-reviewer]

👋 Hi there!

Everything looks good!

_{^{Automatically generated with the help of gpt-3.5-turbo.
Feedback? Please don't hesitate to drop me an email at [email protected].}}

[korbit-ai]

By default, I don't review pull requests opened by bots. If you would like me to review this pull request anyway, you can request a review via the /korbit-review command in a comment.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Note

Free review on us!

CodeRabbit is offering free reviews until Wed Oct 08 2025 to showcase some of the refinements we've made.

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codara-ai-code-review]

Potential issues, bugs, and flaws that can introduce unwanted behavior:

1. Dependency Compatibility - /Tests/POCDijkstra.Tests/POCDijkstra.Tests.csproj: Upgrading the JunitXml.TestLogger package from version 6.1.0 to 7.0.1 may introduce breaking changes or incompatibilities with existing tests or infrastructure if they haven’t been verified against the new version. This could potentially lead to failures in test reporting or logging functionality.

Code suggestions and improvements for better exception handling, logic, standardization, and consistency:

1. Version Pinning - /Tests/POCDijkstra.Tests/POCDijkstra.Tests.csproj: Consider specifying a range for the JunitXml.TestLogger version (e.g., Version="[7.0.0,7.1.0)") instead of a fixed version to provide flexibility and reduce the risk of breaking changes in future upgrades while maintaining compatibility with existing code.
2. Update to Latest Stable Versions - /Tests/POCDijkstra.Tests/POCDijkstra.Tests.csproj: Regularly review and update all package references, including coverlet.msbuild, Microsoft.NET.Test.Sdk, and xunit packages, to the latest stable versions to benefit from performance improvements, bug fixes, and new features. This should be scheduled as part of your development cycle to ensure all dependencies are monitored and updated as necessary.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	junitxml.testlogger@​6.1.0 ⏵ 7.0.1	+1		+2

View full report

[socket-security]

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Block		[email protected] Uses eval. Location: Package overview From: Tests/POCDijkstra.Tests/POCDijkstra.Tests.csproj → nuget/[email protected] ℹ Read more on: This package | This alert | What is dynamic code execution? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Avoid packages that use dynamic code execution like eval(), since this could potentially execute any code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore nuget/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		[email protected] has Filesystem access. Location: Package overview From: Tests/POCDijkstra.Tests/POCDijkstra.Tests.csproj → nuget/[email protected] ℹ Read more on: This package | This alert | What is filesystem access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore nuget/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[guibranco]

Automatically approved by gstraccini[bot]

[guibranco]

@dependabot squash and merge

[github-actions]

Infisical secrets check: ✅ No secrets leaked!

💻 Scan logs

Update Required: Your current package installation script is outdated and will no longer receive updates.
Please update to the new installation script which can be found here https://infisical.com/docs/cli/overview#installation debian section

A new release of infisical is available: 0.38.0 -> 0.41.90

To update, run: sudo apt-get update && sudo apt-get install infisical

3:22PM INF scanning for exposed secrets...
3:22PM INF 141 commits scanned.
3:22PM INF scan completed in 82.5ms
3:22PM INF no leaks found

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[codacy-production]

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
✅ +0.00% (target: -1.00%)	✅ ∅

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (9376f84)	89	86	96.63%
Head commit (ad94450)	89 (+0)	86 (+0)	96.63% (+0.00%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#131)	0	0	∅ (not applicable)

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

[AppVeyorBot]

❌ Build POC-dotnet-Dijkstra 1.1.490 failed (commit df8231d0a1 by @dependabot[bot])

[dependabot]

One of your CI runs failed on this pull request, so Dependabot won't merge it.

Dependabot will still automatically merge this pull request if you amend it and your tests pass.

[dependabot]

Superseded by #132.