chore(deps): update tunit to 1.7.0

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
TUnit	nuget	minor	1.6.28 → 1.7.0
TUnit.AspNetCore	nuget	minor	1.6.28 → 1.7.0
TUnit.Assertions	nuget	minor	1.6.28 → 1.7.0
TUnit.Assertions.FSharp	nuget	minor	1.6.28 → 1.7.0
TUnit.Core	nuget	minor	1.6.28 → 1.7.0
TUnit.Playwright	nuget	minor	1.6.28 → 1.7.0

---

Release Notes

thomhurst/TUnit (TUnit)

v1.7.0: 1.7.0

What's Changed

Other Changes

• feat(analyzers): add NUnit ExpectedResult migration support by @​thomhurst in #​4170
• perf: reduce lock contention in test discovery and scheduling by @​thomhurst in #​4171
• perf: replace redundant allocations with Linq by @​TimothyMakkison in #​4172
• fix: move permissions to workflow level for OIDC token access by @​Copilot in #​4173
• Fix dotnet test documentation to require -- separator for TUnit extension flags by @​Copilot in #​4097
• Fix dotnet test command syntax in documentation for Microsoft.Testing.Platform by @​Copilot in #​4084
• System.Text.Json Assertions for JsonNode, JsonElement, etc. by @​thomhurst in #​4179

Dependencies

• chore(deps): update dependency polyfill to 9.5.0 by @​thomhurst in #​4152
• chore(deps): update tunit to 1.6.28 by @​thomhurst in #​4156
• chore(deps): update verify to 31.9.1 by @​thomhurst in #​4166
• chore(deps): update verify to 31.9.2 by @​thomhurst in #​4168
• chore(deps): update verify to 31.9.3 by @​thomhurst in #​4175

Full Changelog: v1.6.28...v1.7.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 these updates again.

---

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

---

This PR has been generated by Renovate Bot.

[github-actions]

Pull Request Review: TUnit 1.7.0 Dependency Update

✅ Overall Assessment

This is a straightforward and well-structured dependency update PR generated by Renovate Bot. The changes are clean and appropriate.

---

📋 Review Findings

Code Quality: ✅ Excellent

• All version updates are consistent across all packages (1.6.28 → 1.7.0)
• Changes are limited to version numbers only, no unexpected modifications
• Both Directory.Packages.props (central package management) and template project files are updated consistently

Scope: ✅ Appropriate

The PR correctly updates all TUnit package references:

• TUnit (core framework)
• TUnit.AspNetCore
• TUnit.Core
• TUnit.Assertions
• TUnit.Assertions.FSharp
• TUnit.Playwright

All 9 template projects are updated:

• C#, F#, and VB.NET templates
• AspNet, Aspire, and Playwright variants

Release Notes Review: ✅ Good

The 1.7.0 release includes:

• Performance improvements: Reduced lock contention in test discovery/scheduling (perf: reduce lock contention in test discovery and scheduling #4171), LINQ allocation reductions (perf: replace redundant allocations with Linq #4172)
• New features: NUnit ExpectedResult migration support (feat(analyzers): add NUnit ExpectedResult migration support #4170), System.Text.Json assertions (System.Text.Json Assertions for JsonNode, JsonElement, etc. #4179)
• Bug fixes: Documentation and CI/CD improvements

These changes align with TUnit's performance-first philosophy from CLAUDE.md.

---

🔍 Specific Observations

Strengths:

1. Consistency: All packages updated to the same version (no partial updates)
2. Automation: Proper use of Renovate Bot with automerge enabled
3. Semantic versioning: Correctly labeled as MINOR update
4. Template coverage: All project templates updated (important for new users)

No Issues Found:

• ✅ No breaking changes in the release notes
• ✅ No security vulnerabilities mentioned
• ✅ No unexpected file modifications
• ✅ Proper use of central package management

---

🎯 Recommendations

None Required

This is a clean dependency update with no concerns. The PR is ready to merge.

Optional Enhancement (Future Consideration):

Consider adding automated integration tests that run against template projects to catch any breaking changes in dependency updates before they reach users. However, this is outside the scope of this PR.

---

📊 Summary

Category	Rating	Notes
Code Quality	✅ Excellent	Clean, consistent changes
Test Coverage	✅ Adequate	Standard dependency update (CI will validate)
Security	✅ No concerns	Internal package update
Performance	✅ Improved	Release includes perf enhancements
Breaking Changes	✅ None	Minor version bump

---

✅ Approval Recommendation

APPROVED - This PR is ready to merge.

The update is straightforward, properly scoped, and the underlying release (1.7.0) includes valuable performance improvements that align with TUnit's core principles. Auto-merge is appropriately enabled.

[claude]

Code Review: TUnit 1.7.0 Dependency Update

✅ APPROVED - Ready to Merge

This is a clean, well-structured dependency update that follows TUnit conventions perfectly.

---

📋 Review Summary

Changes: Updates TUnit packages from 1.6.28 to 1.7.0 across:

• Central package management (Directory.Packages.props)
• All 9 project templates (C#, F#, VB, AspNet, Aspire, Playwright variants)

Packages updated:

• TUnit, TUnit.Core, TUnit.Assertions, TUnit.AspNetCore, TUnit.Assertions.FSharp, TUnit.Playwright

---

✅ Compliance with CLAUDE.md Guidelines

✅ Performance First - Release 1.7.0 includes:

• Reduced lock contention in test discovery/scheduling
• LINQ allocation optimizations

✅ Modern C# - New System.Text.Json assertions

✅ No Breaking Changes - Correctly tagged as MINOR version bump

✅ Template Consistency - All user-facing templates updated uniformly

---

🔍 Technical Review

Code Quality: ⭐⭐⭐⭐⭐

• Consistent version updates across all references
• No unexpected file modifications
• Proper use of centralized package management

Security: ✅ No concerns

• Internal package update from same repository
• Snyk security check: PASSED

Testing: ✅ Adequate

• Standard dependency update
• CI validation will catch any integration issues

Performance: ✅ Improved

• Release includes performance enhancements aligned with TUnit core principles

---

💡 Key Observations

1. Release highlights (from v1.7.0):

   • NUnit ExpectedResult migration support (analyzer)
   • Performance improvements in critical paths
   • Enhanced System.Text.Json assertion support

2. Automerge enabled - Appropriate for automated dependency updates from Renovate

3. All templates updated - Important for consistency in new user experience

---

✅ Final Recommendation

Ready to merge. This PR is exactly what a dependency update should be: minimal, consistent, and includes valuable improvements in the underlying release.

No action required - automerge can proceed.

---

Reviewed per CLAUDE.md guidelines - focusing on performance, modern .NET practices, and reliability.

[claude]

Independent Code Review: TUnit 1.7.0 Update

Summary

This PR updates TUnit package references from 1.6.28 to 1.7.0 across the codebase. After independent analysis, I concur with the previous reviews.

---

✅ Code Quality Analysis

Consistency: Excellent

• All 6 TUnit packages updated uniformly to 1.7.0
• Central package management (Directory.Packages.props) + 9 template projects
• No partial updates or version mismatches

Scope Verification:

✓ TUnit (core)
✓ TUnit.Core  
✓ TUnit.Assertions
✓ TUnit.Assertions.FSharp
✓ TUnit.AspNetCore
✓ TUnit.Playwright

Template Coverage (all variants updated):

• C# / F# / VB.NET
• AspNet / Aspire / Playwright variations

---

🔍 CLAUDE.md Compliance Check

Per project guidelines, I verified:

✅ Performance First - v1.7.0 includes:

• Reduced lock contention in test discovery (perf: reduce lock contention in test discovery and scheduling #4171)
• LINQ allocation optimizations (perf: replace redundant allocations with Linq #4172)

✅ Modern C# - System.Text.Json assertions added (#4179)

✅ No Breaking Changes - MINOR semver bump (1.6.x → 1.7.0)

✅ No VSTest Dependencies - Only Microsoft.Testing.Platform used

---

🚨 Issues Found

None. This is a textbook dependency update.

---

📊 Technical Assessment

Area	Status	Notes
Breaking Changes	✅ None	Minor version bump only
Security	✅ Clear	Internal package update
Performance	✅ Improved	Lock contention & allocation fixes
AOT Compatibility	✅ Maintained	No API surface changes
Test Impact	✅ Low risk	Standard dependency update

---

💡 Additional Observations

1. Release Quality: v1.7.0 includes meaningful improvements aligned with TUnit's core principles
2. Automation: Properly configured Renovate Bot with automerge
3. User Impact: Template updates ensure new users get latest version
4. No Snapshot Changes: Dependency update doesn't affect source generator output

---

✅ Recommendation

APPROVED - Ready to merge immediately.

This is exactly what dependency management automation should look like: clean, consistent, and low-risk with tangible improvements in the underlying release.

Automerge can proceed without intervention.

---

Review conducted per CLAUDE.md mandatory rules and TUnit development guidelines.

[github-actions]

Summary

Updates TUnit package references from 1.6.28 to 1.7.0 across central package management and all project templates.

Critical Issues

None found ✅

Previous Review Status

Three previous approvals all reached the same conclusion: this is a clean, low-risk dependency update. I concur with their assessments.

TUnit Rules Compliance

Verified against CLAUDE.md critical rules:

• ✅ No dual-mode concerns (not touching source generator or engine code)
• ✅ No snapshot test concerns (no generator output changes)
• ✅ No public API changes (dependency versions only)
• ✅ No AOT concerns (no reflection changes)
• ✅ No performance concerns (not touching hot paths)
• ✅ No VSTest usage (dependency update only)

Key observations:

• All 6 TUnit packages updated consistently to 1.7.0
• All 9 template projects updated uniformly
• Release notes show performance improvements and new features aligned with TUnit principles
• No code changes, only version number updates

Verdict

✅ APPROVE - No critical issues

This is exactly what a dependency update should be: minimal, consistent, and safe. Ready to merge.