chore(deps): update dependency tunit to 0.85.0

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
TUnit	nuget	minor	0.81.7 -> 0.85.0

---

Release Notes

thomhurst/TUnit (TUnit)

v0.85.0: 0.85.0

What's Changed

Breaking Changes 🛠

• refactor: restructure TestContext for clarity and intellisense discoverability by @​thomhurst in #​3584

See more information here: https://tunit.dev/docs/migration/testcontext-interface-organization

👒 Dependencies

• chore(deps): update tunit to 0.81.7 by @​thomhurst in #​3583

Full Changelog: v0.81.7...v0.85.0

---

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 this update again.

---

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

---

This PR has been generated by Renovate Bot.

[claude]

Claude finished @thomhurst's task —— View job

---

Pull Request Review

Todo List:

• Read and analyze changed template files
• Review breaking changes from release notes
• Check for potential compatibility issues
• Assess security and performance implications
• Provide comprehensive review feedback

---

✅ Code Quality Assessment

Overall: This is a well-executed dependency update with minimal risk. The changes are clean, automated, and scope-appropriate.

📋 Review Findings

✅ Positive Aspects

1. Clean Version Update: All template files correctly updated from 0.81.7 to 0.85.0
2. Consistent Scope: Changes limited to template project files only
3. Automated Process: Renovate bot ensures systematic updates
4. Breaking Change Documentation: Comprehensive migration guide provided

⚠️Issues Found

1. Version Inconsistency in F# Template (TUnit.Templates/content/TUnit.FSharp/TestProject.fsproj:14)

   <PackageReferenceInclude="TUnit.Assertions.FSharp"Version="0.81.7" />

   • This package reference wasn't updated to 0.85.0
   • Could cause version conflicts or confusion for F# template users

2. Mixed TUnit Versions in Central Package Management (Directory.Packages.props:86-88)

   <PackageVersionInclude="TUnit"Version="0.85.0" />
   <PackageVersionInclude="TUnit.Core"Version="0.85.0" />
   <PackageVersionInclude="TUnit.Assertions"Version="0.81.7" /> 

   • TUnit.Assertions is still at 0.81.7 while core packages are at 0.85.0

🔄 Breaking Changes Analysis

The release notes mention TestContext restructuring as a breaking change:

• Impact: Templates themselves are not affected - they don't contain TestContext usage

• User Impact: Template users may need to update existing test code if they use:

  • TestContext.Current.CustomHookExecutor → TestContext.Current.Execution.CustomHookExecutor
  • TestContext.Current.DisplayNameFormatter → TestContext.Current.Metadata.DisplayNameFormatter
  • TestContext.Current.AddLinkedCancellationToken() → TestContext.Current.Execution.AddLinkedCancellationToken()

• Mitigation: Breaking changes are well-documented with migration guide, and backwards compatibility is maintained.

🔒 Security Assessment

• No security concerns: Version update from trusted source
• Dependency chain: All changes are first-party TUnit packages
• No new vulnerabilities introduced

🚀 Performance Considerations

• Zero performance impact on templates themselves
• Upstream improvements: TUnit 0.85.0 includes interface organization that provides "zero-allocation design" benefits
• Template generation: No changes to template structure or build performance

🧪 Test Coverage

• Template-level: No test logic changes required
• Integration: Templates will automatically use new TUnit version when instantiated
• User testing: Users should test their existing TestContext usage against breaking changes

🎯 Recommendations

Immediate Actions Needed:

1. Fix F# template version inconsistency: Update TUnit.Assertions.FSharp to 0.85.0 in F# template
2. Consider updating TUnit.Assertions: Update to 0.85.0 in central package management if available

Documentation:

1. Template documentation: Consider adding migration notes to template README files
2. Breaking change communication: Users should be made aware of TestContext changes when using templates

📊 Risk Assessment

Risk Level	Component	Details
🟢 Low	Template structure	No breaking changes to template format
🟡 Medium	Version consistency	F# template and central packages have mismatched versions
🟢 Low	User impact	Breaking changes are backwards compatible
🟢 Low	Security	Trusted first-party dependency update

✅ Approval Recommendation

APPROVE with minor fixes needed

The PR is fundamentally sound but requires fixing the version inconsistencies mentioned above. The dependency update itself is safe and well-documented.