[dependabot]

Updates the requirements on junitparser to permit the latest version.

Changelog

Sourced from junitparser's changelog.

[5.0.3] - 2026-08-31

Fixed

• Issue 177: Fix 177 different behavior of + and +=.

[5.0.2] - 2026-08-31

Fixed

• Issue 180: Fix add_testsuite regression caused by 5.0.1.

[5.0.1] - 2026-06-04

Fixed

• __add__: mutated arguments after operation thanks @​miguelflor.

[5.0.0] - 2026-03-28

Breaking

• Drop support for Python 3.9 and below. Use version 4 if you're still on an older Python version.
• Update type annotations thanks to @​nkr0
• Make TestCase support Properties tags thanks to @​eap

[4.0.2] - 2025-06-23

Fixed

• write_xml - now supports Path from pathlib.

[4.0.1] - 2025-06-23

Fixed

• write_xml - Remove encoding kwarg to fix binary mode doesn't take an encoding argument

[4.0.0] - 2025-06-22

Breaking

• Renamed argument filepath of methods write_xml, TestSuite.write, and JUnitXml.write to file_or_filename, as these methods now support file objects and file-like objects.

• Turned positional argument pretty of methods write_xml, TestSuite.write, and JUnitXml.write into keyword argument. Use as write_xml(obj, filename, pretty=True) and obj.write(filename, pretty=True), respectively.

• Removed argument to_console from methods write_xml, TestSuite.write, and JUnitXml.write. Instead, use write_xml(obj, sys.stdout) and obj.write(sys.stdout), respectively.

• Renamed argument filepath of method JUnitXml.fromfile to file, to reflect that this method supports file objects, file-like objects, and urls.

• Setter method TestCase.result used to ignore values of invalid types. This method now throws a ValueError instead.

• Method xunit2.TestCase.add_rerun_result has been renamed to add_interim_result result to better reflect class hierarchy of interim (rerun and flaky) results.

• Methods JUnitXml.fromfile, JUnitXml.fromstring, JUnitXml.fromroot always return a JUnitXml instance. Earlier versions return a TestSuite instance when the root of the file / string / element is a <TestSuite>. A JUnitXml instance has already been returned by earlier versions when the root of the file / string / element is a <TestSuites>.

  If you want to create a TestSuite instance from a <TestSuite> element, use

  TestSuite.fromelem(elem)

[3.1.2] - 2024-08-31

Fixed

• the TestCase.result type annotation

... (truncated)

Commits

• bb12f2d fix #177
• 3c28cf9 fix: #180 add_testsuite regression
• 0dfbcb6 Update uv-build requirement from <0.12.0,>=0.11.7 to >=0.11.7,<0.13.0 (#181)
• d98bdb7 release 5.0.1
• c907926 Fix add: mutated arguments after operation (#178)
• 89dde05 ci: add PyPI publish attestations (#179)
• ab3451b Use uv and ruff (#176)
• 51b7f29 Merge branch 'master' of https://github.com/weiwei/junitparser
• 5950f59 release 5.0
• 35ec8d6 Make TestCase support Properties tags (#171)
• Additional 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 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 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)

[openshift-ci]

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a RedHatQE member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.