chore(deps): update tunit to 1.37.36

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
TUnit	nuget	patch	1.37.24 → 1.37.36
TUnit.AspNetCore	nuget	patch	1.37.24 → 1.37.36
TUnit.Assertions	nuget	patch	1.37.24 → 1.37.36
TUnit.Assertions.FSharp	nuget	patch	1.37.24 → 1.37.36
TUnit.Core	nuget	patch	1.37.24 → 1.37.36
TUnit.Engine	nuget	patch	1.37.24 → 1.37.36
TUnit.Playwright	nuget	patch	1.37.24 → 1.37.36

---

Release Notes

thomhurst/TUnit (TUnit)

v1.37.36: 1.37.36

What's Changed

Other Changes

• fix(telemetry): remove duplicate HTTP client spans by @​thomhurst in #​5668

Full Changelog: v1.37.35...v1.37.36

v1.37.35: 1.37.35

What's Changed

Other Changes

• Add TUnit.TestProject.Library to the TUnit.Dev.slnx solution file by @​Zodt in #​5655
• fix(aspire): preserve user-supplied OTLP endpoint (#​4818) by @​thomhurst in #​5665
• feat(aspire): emit client spans for HTTP by @​thomhurst in #​5666

Dependencies

• chore(deps): update dependency dotnet-sdk to v10.0.203 by @​thomhurst in #​5656
• chore(deps): update microsoft.aspnetcore to 10.0.7 by @​thomhurst in #​5657
• chore(deps): update tunit to 1.37.24 by @​thomhurst in #​5659
• chore(deps): update microsoft.extensions to 10.0.7 by @​thomhurst in #​5658
• chore(deps): update aspire to 13.2.3 by @​thomhurst in #​5661
• chore(deps): update dependency microsoft.net.test.sdk to 18.5.0 by @​thomhurst in #​5664

New Contributors

• @​Zodt made their first contribution in #​5655

Full Changelog: v1.37.24...v1.37.35

---

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.

[claude]

Code Review

This is a Renovate bot PR bumping TUnit.AspNetCore from 1.37.24 → 1.37.35 in Directory.Packages.props.

What's in 1.37.35

Per the release notes, the intermediate versions include:

• fix(aspire): preserve user-supplied OTLP endpoint (#4818)
• feat(aspire): emit client spans for HTTP
• Several dependency bumps (dotnet-sdk, aspnetcore, aspire, microsoft.extensions, microsoft.net.test.sdk)

Observation: Version Mismatch Within TUnit Family

The change leaves the TUnit package family in a split state:

<PackageVersion Include="TUnit" Version="1.37.24" />
<PackageVersion Include="TUnit.AspNetCore" Version="1.37.35" />  <!-- bumped -->
<PackageVersion Include="TUnit.Core" Version="1.37.24" />
<PackageVersion Include="TUnit.Engine" Version="1.37.24" />
<PackageVersion Include="TUnit.Assertions" Version="1.37.24" />

If TUnit.AspNetCore has a hard dependency on TUnit.Core >= 1.37.35, this could cause a runtime conflict. It's worth confirming that TUnit.AspNetCore 1.37.35 is compatible with TUnit.Core/Engine 1.37.24, or whether all packages should be bumped together.

If the packages are independently versioned and TUnit.AspNetCore carries its own release cadence separate from the core packages, this is fine as-is. But if they share a tight internal API surface (which is common for framework extension packages), keeping versions in sync avoids subtle breakage.

Change Itself

The single-line diff is correct and minimal. No concerns with the mechanical change.

Verdict: Approve with the caveat above — worth a quick sanity-check that TUnit.AspNetCore 1.37.35 does not require a newer TUnit.Core than 1.37.24.

[claude]

Code Review

This is a Renovate bot PR bumping TUnit.AspNetCore from 1.37.24 → 1.37.35 in Directory.Packages.props.

What's in 1.37.35

Per the release notes, the intermediate versions include:

• fix(aspire): preserve user-supplied OTLP endpoint (#4818)
• feat(aspire): emit client spans for HTTP
• Several dependency bumps (dotnet-sdk, aspnetcore, aspire, microsoft.extensions, microsoft.net.test.sdk)

Observation: Version Mismatch Within TUnit Family

The change leaves the TUnit package family in a split state:

<PackageVersion Include="TUnit" Version="1.37.24" />
<PackageVersion Include="TUnit.AspNetCore" Version="1.37.35" />  <!-- bumped -->
<PackageVersion Include="TUnit.Core" Version="1.37.24" />
<PackageVersion Include="TUnit.Engine" Version="1.37.24" />
<PackageVersion Include="TUnit.Assertions" Version="1.37.24" />

If TUnit.AspNetCore has a hard dependency on TUnit.Core >= 1.37.35, this could cause a runtime conflict. It's worth confirming that TUnit.AspNetCore 1.37.35 is compatible with TUnit.Core/Engine 1.37.24, or whether all packages should be bumped together.

If the packages are independently versioned and TUnit.AspNetCore carries its own release cadence separate from the core packages, this is fine as-is. But if they share a tight internal API surface (which is common for framework extension packages), keeping versions in sync avoids subtle breakage.

Change Itself

The single-line diff is correct and minimal. No concerns with the mechanical change.

Verdict: Approve with the caveat above — worth a quick sanity-check that TUnit.AspNetCore 1.37.35 does not require a newer TUnit.Core than 1.37.24.

[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

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes. Give us feedback}

[claude]

Code Review: Dependency Bump — TUnit 1.37.24 → 1.37.35

Previous Review Follow-up: An earlier review from this session raised a version mismatch concern; that was based on a misreading of the diff. The actual diff correctly bumps all 7 TUnit family packages together, so there is no concern there.

---

Summary

This is a Renovate Bot–generated dependency bump updating the entire TUnit package family (7 packages) from 1.37.24 to 1.37.35.

What Changed

File	Change
Directory.Packages.props	Central version pin for 6 packages bumped
TUnit.Templates/content/*/\*.csproj/.fsproj/.vbproj	Pinned versions in 5 template projects bumped

Analysis

✅ Version coherence — All 7 packages (TUnit, TUnit.Assertions, TUnit.Assertions.FSharp, TUnit.AspNetCore, TUnit.Core, TUnit.Engine, TUnit.Playwright) are bumped in perfect lockstep. No version splits.

✅ Template parity — The template projects under TUnit.Templates/content/ are updated in sync, so newly scaffolded projects will use the same version as the monorepo itself.

✅ Central version management respected — Projects using Central Package Management (Directory.Packages.props) are updated at the root, not scattered across individual .csproj files. Template projects that cannot use CPM are updated directly — both patterns are correct.

✅ Release notes are substantive — The 1.37.35 release includes a bug fix for Aspire OTLP endpoint preservation (#4818), new HTTP client span emission, and a solution file addition. All are straightforward improvements with no breaking changes.

✅ Codacy clean — No new issues or complexity introduced.

Verdict

This is a clean, well-formed dependency update. The lockstep versioning strategy across the TUnit family is correctly applied. No concerns.

[claude]

Code Review: Dependency Bump — TUnit 1.37.24 → 1.37.35

Previous review context: Earlier reviews in this session are already on record. This is a confirming review for the current head commit.

Summary

Renovate Bot–generated patch bump of all 7 TUnit family packages from 1.37.24 → 1.37.35. This is a clean, low-risk update.

Checklist

• Version coherence — All 7 packages (TUnit, TUnit.Assertions, TUnit.Assertions.FSharp, TUnit.AspNetCore, TUnit.Core, TUnit.Engine, TUnit.Playwright) move in perfect lockstep. No split versions.
• Central Package Management — Directory.Packages.props is the single source of truth for the monorepo. Updated correctly.
• Template parity — The 5 template .csproj/.fsproj/.vbproj files under TUnit.Templates/content/ are updated in sync, so scaffolded projects get the same version.
• Release notes are substantive — 1.37.35 includes a bug fix for Aspire OTLP endpoint preservation (#4818), new HTTP client span emission for Aspire, and a solution file addition. No breaking changes.
• Codacy clean — 0 new issues, 0 complexity delta.

Verdict

No concerns. The diff is mechanically correct and the release content is safe to adopt.

[claude]

Code Review — Routine Dependency Bump

This is a clean, routine Renovate Bot patch bump of all 7 TUnit family packages from 1.37.24 → 1.37.36.

Checklist

• Version coherence — All 7 packages (TUnit, TUnit.Assertions, TUnit.Assertions.FSharp, TUnit.AspNetCore, TUnit.Core, TUnit.Engine, TUnit.Playwright) are bumped in perfect lockstep. No mismatches.
• CPM correctness — Directory.Packages.props is the authoritative source for the monorepo, updated correctly.
• Template parity — The 5 template project files (.fsproj, .csproj, .vbproj) are updated with direct version pins, which is correct since they live outside the CPM boundary.
• Release notes — v1.37.25–v1.37.36 contain bug fixes (telemetry duplicate spans, Aspire OTLP endpoint), one additive feature (HTTP client spans for Aspire), and dependency updates. No breaking changes.
• Previous reviews addressed — The earlier false concern about a version mismatch was already corrected and confirmed clean in subsequent reviews.

No issues found. The change is mechanical, safe, and follows the repo's established dependency management patterns.

Approved.