[renovate]

This PR updates quick-junit to v0.8.0. The original renovate description of the bump to v0.7.0 is below.

---

This PR contains the following updates:

Package	Type	Update	Change	Pending
quick-junit	workspace.dependencies	minor	0.6.0 → 0.7.0	0.8.0

---

Release Notes

nextest-rs/quick-junit (quick-junit)

v0.7.0

Compare Source

Changed

Skipped test counts

Skipped test counts are now reported via the skipped attribute rather than disabled. For <testsuite>, skipped matches the llg schema and the Jenkins junit-10 schema, as well as pytest and Maven Surefire.

• Each <testsuite> now emits skipped="N", and the root <testsuites> element now emits an aggregated skipped="N" count. Previously the root didn't carry a skip count at all.
• Root-level skipped is a quick-junit extension. It follows the modern JUnit convention (as documented, for example, by testmoapp/junitxml) and is similar to quick-junit's existing extensions such as uuid.
• TestSuite's disabled field has been renamed to skipped.
• Report gains new public skipped and disabled fields, and Report::add_test_suite now aggregates skip counts into Report::skipped.

disabled is now modeled as a separate optional count on both Report and TestSuite, distinct from skipped. (disabled is intended to count tests that are disabled by design, such as googletest's DISABLED_-prefixed tests. Note, however, that quick-junit doesn't have a notion of disabled tests at the moment.)

Other changes

• Report is now #[non_exhaustive], consistent with TestSuite and TestCase. Construct it via Report::new and then assign fields, so that future field additions are non-breaking.
• Childless <testsuite> and <testcase> elements are now serialized as self-closing tags (for example, <testcase name="my-test"/> rather than <testcase name="my-test"></testcase>). The output is semantically identical XML, only more compact and idiomatic. The deserializer already accepted these self-closing forms, so serializing them means round-trip tests now cover those parse paths.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "before 4am on Wednesday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[astral-sh-bot]

Typing conformance results

No changes detected ✅

Current numbers

The percentage of diagnostics emitted that were expected errors held steady at 98.15%. The percentage of expected errors that received a diagnostic held steady at 98.07%. The number of fully passing files held steady at 133/146.

[astral-sh-bot]

Memory usage report

Memory usage unchanged ✅

[astral-sh-bot]

ecosystem-analyzer results

No diagnostic changes detected ✅

Flaky changes detected. This PR summary excludes flaky changes; see the HTML report for details.

Full report with detailed diff (timing results)

[astral-sh-bot]

ruff-ecosystem results

Linter (stable)

✅ ecosystem check detected no linter changes.

Linter (preview)

✅ ecosystem check detected no linter changes.

Formatter (stable)

✅ ecosystem check detected no format changes.

Formatter (preview)

ℹ️ ecosystem check encountered format errors. (no format changes; 1 project error)

openai/openai-cookbook (error)

ruff format --preview --exclude examples/mcp/databricks_mcp_cookbook.ipynb,examples/chatgpt/gpt_actions_library/gpt_action_google_drive.ipynb,examples/chatgpt/gpt_actions_library/gpt_action_redshift.ipynb,examples/chatgpt/gpt_actions_library/gpt_action_salesforce.ipynb,

warning: Detected debug build without --no-cache.
error: Encountered error: No such file or directory (os error 2)
error: Encountered error: No such file or directory (os error 2)
error: Encountered error: No such file or directory (os error 2)
error: Encountered error: No such file or directory (os error 2)
error: Encountered error: No such file or directory (os error 2)
error: Encountered error: No such file or directory (os error 2)
error: Encountered error: No such file or directory (os error 2)
error: Encountered error: No such file or directory (os error 2)
error: Encountered error: No such file or directory (os error 2)
error: Encountered error: No such file or directory (os error 2)
error: Encountered error: No such file or directory (os error 2)
error: Encountered error: No such file or directory (os error 2)
error: Encountered error: No such file or directory (os error 2)

[ntBre]

I'm not totally sure whether this is breaking or not. The snapshot diffs look like this:

 <?xml version="1.0" encoding="UTF-8"?>
-<testsuites name="ty" tests="2" failures="2" errors="0">
-    <testsuite name="/syntax_errors.py" tests="2" disabled="0" errors="0" failures="2" package="org.ty">
+<testsuites name="ty" tests="2" skipped="0" failures="2" errors="0">
+    <testsuite name="/syntax_errors.py" tests="2" skipped="0" errors="0" failures="2" package="org.ty">
         <testcase name="org.ty.invalid-syntax" classname="/syntax_errors" line="1" column="15">
             <properties>
                 <property name="severity" value="error"/>
             </properties>

where the skipped attribute has been added to the testsuites tag, and the disabled attribute has been replaced by skipped in the singular testsuite tag. We don't actually set disabled in our JUnit code, so this doesn't really affect the output we intentionally generate, but it affects the schema. The release notes claim that this change matches at least a few consumer schemas:

Skipped test counts are now reported via the skipped attribute rather than disabled. For <testsuite>, skipped matches the llg schema and the Jenkins junit-10 schema, as well as pytest and Maven Surefire.

but at the same time this was obviously considered a breaking quick-junit release, and part of this is an intentional extension:

Root-level skipped is a quick-junit extension. It follows the modern JUnit convention (as documented, for example, by testmoapp/junitxml) and is similar to quick-junit's existing extensions such as uuid.

I'm curious to see if this triggers a breaking nextest release too since they merged the bump in nextest-rs/nextest#3479 already. I think for us, I would conservatively consider this a breaking change and defer it to the next minor release without some other reason to upgrade earlier.

[MichaReiser]

bundling this into the next minor seems reasonable

[codspeed]

Merging this PR will not alter performance

✅ 211 untouched benchmarks

---

_{Comparing renovate/quick-junit-0.x (6fc9a0e) with brent/0.17.0 (c9958ca)}

[ntBre]

The only change needed here was updating the snapshots. After doing that, I saw that 0.8 was also pending on renovate. It was released 2 weeks ago, so I tried bumping that too, with no additional changes needed, as we weren't using an affected API.