chore(deps): update tunit to 1.34.0

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
TUnit	nuget	minor	1.33.0 → 1.34.0
TUnit.AspNetCore	nuget	minor	1.33.0 → 1.34.0
TUnit.Assertions	nuget	minor	1.33.0 → 1.34.0
TUnit.Assertions.FSharp	nuget	minor	1.33.0 → 1.34.0
TUnit.Core	nuget	minor	1.33.0 → 1.34.0
TUnit.Engine	nuget	minor	1.33.0 → 1.34.0
TUnit.Playwright	nuget	minor	1.33.0 → 1.34.0

---

Release Notes

thomhurst/TUnit (TUnit)

v1.34.0: 1.34.0

What's Changed

Other Changes

• refactor: move CorrelatedTUnitLogger to TUnit.Logging.Microsoft and auto-inject handlers by @​thomhurst in #​5532
• feat: add Dev Drive setup for Windows in CI workflow by @​thomhurst in #​5544
• fix: start session activity before discovery so discovery spans parent correctly by @​thomhurst in #​5534
• feat: cross-process test log correlation via OTLP receiver by @​thomhurst in #​5533
• refactor: use natural OTEL trace propagation instead of synthetic TraceIds by @​thomhurst in #​5557
• fix: route ITestOutput writes through synchronized ConcurrentStringWriter by @​thomhurst in #​5558

Dependencies

• chore(deps): update tunit to 1.33.0 by @​thomhurst in #​5527
• chore(deps): update dependency dompurify to v3.4.0 by @​thomhurst in #​5537
• chore(deps): update dependency docusaurus-plugin-llms to ^0.3.1 by @​thomhurst in #​5541
• chore(deps): update dependency microsoft.sourcelink.github to 10.0.202 by @​thomhurst in #​5543
• chore(deps): update dependency microsoft.entityframeworkcore to 10.0.6 by @​thomhurst in #​5542
• chore(deps): update dependency microsoft.templateengine.authoring.templateverifier to 10.0.202 by @​thomhurst in #​5546
• chore(deps): update dependency microsoft.templateengine.authoring.cli to v10.0.202 by @​thomhurst in #​5545
• chore(deps): update dependency system.commandline to 2.0.6 by @​thomhurst in #​5547
• chore(deps): update microsoft.aspnetcore to 10.0.6 by @​thomhurst in #​5548
• chore(deps): update dependency nuget.protocol to 7.3.1 by @​thomhurst in #​5549
• chore(deps): update microsoft.extensions to 10.0.6 by @​thomhurst in #​5550
• chore(deps): update dependency dotnet-sdk to v10.0.202 by @​thomhurst in #​5551
• chore(deps): update opentelemetry by @​thomhurst in #​5552
• chore(deps): update microsoft.extensions to 10.5.0 by @​thomhurst in #​5554

Full Changelog: v1.33.0...v1.34.0

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

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

---

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

---

This PR has been generated by Renovate Bot.

[azure-pipelines]

Azure Pipelines:
1 pipeline(s) were filtered out due to trigger conditions.

[claude]

Dependency Update Review: TUnit 1.33.0 → 1.34.0

This is a Renovate-generated dependency bump updating 7 TUnit packages (TUnit, TUnit.AspNetCore, TUnit.Assertions, TUnit.Assertions.FSharp, TUnit.Core, TUnit.Engine, TUnit.Playwright) from 1.33.0 to 1.34.0 across Directory.Packages.props and the template project files.

What changed in 1.34.0

Based on the release notes, the notable functional changes in 1.34.0 include:

• refactor: move CorrelatedTUnitLogger to TUnit.Logging.Microsoft and auto-inject handlers (#5532)
• feat: cross-process test log correlation via OTLP receiver (#5533)
• fix: start session activity before discovery so discovery spans parent correctly (#5534)
• refactor: use natural OTEL trace propagation instead of synthetic TraceIds (#5557)
• fix: route ITestOutput writes through synchronized ConcurrentStringWriter (#5558)

The ITestOutput concurrency fix (#5558) and the OTEL session span ordering fix (#5534) are particularly meaningful correctness improvements worth picking up.

Observations and Concerns

Inconsistent version pinning across template projects

The diff updates 5 template project files, but two template projects are not updated and have diverged from the others:

• TUnit.Templates/content/TUnit/TestProject.csproj — uses a floating version "1.*", so it picks up any 1.x release automatically and is unaffected.
• TUnit.Templates/content/TUnit.Aspire.Starter/ExampleNamespace.TestProject/ExampleNamespace.TestProject.csproj — pinned to TUnit.Aspire 1.14.0, a completely different package not in scope here.
• TUnit.Templates/content/TUnit.Aspire.Test/ExampleNamespace.csproj — same, pinned to TUnit.Aspire 1.14.0.

The two Aspire template projects referencing TUnit.Aspire at 1.14.0 look significantly stale relative to the 1.34.0 packages being updated here. It would be worth checking whether TUnit.Aspire has also released updates that should accompany this bump.

Directory.Packages.props vs. template project files — dual version management

The template project files (TUnit.Templates/content/*/TestProject.*proj) pin their own explicit versions independent of Directory.Packages.props. This creates a maintenance burden: each Renovate bump must update both the central props file and each template project file individually. Some template projects use Version="1.*" (the floating wildcard), while others use hard pins. A more consistent approach across all templates would reduce the chance of partial updates slipping through.

Consider whether the template project files should all adopt Version="1.*" (as TUnit/TestProject.csproj already does), which would eliminate the need for Renovate to touch those files on every minor release. Since these are starter templates rather than production code, a floating 1.* constraint is a reasonable end-user experience.

No source-gen / reflection mode impact

This PR only changes package version numbers and has no effect on the source generator, reflection engine, or any runtime behaviour. The dual-mode requirement and AOT compatibility concerns do not apply here.

Auto-merge is enabled — appropriate for this PR

Given that this is a patch-level dependency update to TUnit's own packages (essentially self-referential: the repo itself depends on its own published NuGet), auto-merge via squash is appropriate. CI checks (integration-tests, modularpipeline across platforms) will gate the merge.

Summary

The update is correct and straightforward. The only actionable items to consider:

1. Check TUnit.Aspire versions in TUnit.Aspire.Starter and TUnit.Aspire.Test templates — 1.14.0 looks stale.
2. Consider standardizing template project version constraints to 1.* (floating) to reduce the number of files Renovate must touch on every minor release.

No blocking issues. This is a routine, safe dependency bump.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity

Metric	Results
Complexity	0

View in Codacy

_{TIP This summary will be updated as you push new changes. Give us feedback}