chore(deps): update tunit to 1.17.36

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
TUnit	nuget	patch	1.17.29 → 1.17.36
TUnit.AspNetCore	nuget	patch	1.17.29 → 1.17.36
TUnit.Assertions	nuget	patch	1.17.29 → 1.17.36
TUnit.Assertions.FSharp	nuget	patch	1.17.29 → 1.17.36
TUnit.Core	nuget	patch	1.17.29 → 1.17.36
TUnit.Engine	nuget	patch	1.17.29 → 1.17.36
TUnit.Playwright	nuget	patch	1.17.29 → 1.17.36

---

Release Notes

thomhurst/TUnit (TUnit)

v1.17.36: 1.17.36

What's Changed

Other Changes

• feat(mocks): concise API — inline lambdas, untyped Any(), global static import by @​thomhurst in #​5017

Dependencies

• chore(deps): update tunit to 1.17.29 by @​thomhurst in #​5008
• chore(deps): update aspire to 13.1.2 by @​thomhurst in #​5010
• chore(deps): update dependency polyfill to 9.12.0 by @​thomhurst in #​5012
• chore(deps): update dependency polyfill to 9.12.0 by @​thomhurst in #​5011
• chore(deps): update actions/download-artifact action to v8 by @​thomhurst in #​5014

Full Changelog: v1.17.29...v1.17.36

---

Configuration

📅 Schedule: 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 routine Renovate Bot dependency update bumping all TUnit packages from 1.17.29 → 1.17.36 (patch version bump).

Summary

All 7 TUnit package references have been updated consistently across:

• Directory.Packages.props (centralized version management)
• Template project files (TUnit.Templates/content/*)

Assessment

Looks good. This is a clean, correctly-scoped patch update with no issues to flag:

• Consistency: All TUnit packages are bumped to the same version (1.17.36), which is correct — these packages are tightly coupled and should always be kept in sync.
• Scope: Only version strings changed; no structural modifications to project files.
• Coverage: The Directory.Packages.props centralized versions are updated, and so are the template project files that pin their own versions directly (expected, since templates are standalone and don't use Central Package Management from the main repo).
• Auto-merge enabled: Appropriate for a patch-level dependency update on packages this repo owns.

No concerns. Safe to merge.