[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
TUnit	nuget	patch	0.61.2 -> 0.61.6
TUnit.Assertions	nuget	patch	0.61.2 -> 0.61.6
TUnit.Assertions.FSharp	nuget	patch	0.61.2 -> 0.61.6
TUnit.Core	nuget	patch	0.61.2 -> 0.61.6
TUnit.Playwright	nuget	patch	0.61.2 -> 0.61.6

---

Release Notes

thomhurst/TUnit (TUnit)

v0.61.6: 0.61.6

What's Changed

🏕 Changes

• feat: add support for special floating-point values (NaN, Infinity) by @​thomhurst in #​3158
• fix: ensure After(Test) hooks execute before test instance disposal by @​thomhurst in #​3159

👒 Dependencies

• chore(deps): update tunit to 0.61.2 by @​thomhurst in #​3149

Full Changelog: v0.61.2...v0.61.6

---

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]

Claude finished @thomhurst's task —— View job

---

Code Review: TUnit Package Updates (0.61.2 → 0.61.6)

Todo List:

• Read changed files to understand update scope
• Review TUnit development guidelines
• Analyze release notes for breaking changes
• Check for potential compatibility issues
• Provide comprehensive review feedback

---

📋 Review Summary

Overall Assessment: ✅ APPROVED - This is a safe, routine package update with beneficial bug fixes.

🔍 Code Quality & Best Practices

✅ Excellent adherence to standards:

• Centralized package management via Directory.Packages.props - follows .NET best practices
• Consistent version updates across all TUnit packages (0.61.2 → 0.61.6)
• Template files properly updated to maintain consistency
• All changes are version-only updates with no code modifications

🐛 Potential Issues

✅ No issues identified:

• Version increments are minor patch releases (0.61.2 → 0.61.6)
• No breaking changes in the release notes
• All package references use the same version, avoiding dependency conflicts
• Template projects maintain compatibility with updated packages

🚀 Performance Considerations

✅ Performance improvements expected:

• Release 0.61.6 includes bug fixes for After(Test) hooks execution order
• The hook fix ensures proper test instance disposal timing, potentially improving memory management
• New NaN/Infinity support adds functionality without performance overhead

🔒 Security Concerns

✅ No security issues:

• Updates are from the same trusted source (TUnit project itself)
• No external dependencies or third-party packages involved
• Version updates don't introduce new attack vectors

🧪 Test Coverage

⚠️ Recommendation: According to TUnit's CLAUDE.md guidelines, snapshot tests should be run when making changes that could affect source generator output or public APIs:

# Recommended to run before merging:
dotnet test TUnit.Core.SourceGenerator.Tests
dotnet test TUnit.PublicAPI

While this is just a version bump, the underlying TUnit changes include new floating-point value support that could potentially affect generated code.

📊 Changes Analysis

Files Modified (9 total):

• Directory.Packages.props: Updated TUnit, TUnit.Core, and TUnit.Assertions versions
• Template project files: Updated package references to maintain consistency

Packages Updated:

• TUnit: 0.61.2 → 0.61.6
• TUnit.Assertions: 0.61.2 → 0.61.6
• TUnit.Assertions.FSharp: 0.61.2 → 0.61.6
• TUnit.Core: 0.61.2 → 0.61.6
• TUnit.Playwright: 0.61.2 → 0.61.6

✨ Notable Improvements in 0.61.6

1. NaN/Infinity Support: Added support for special floating-point values in code generation
2. Hook Execution Fix: Ensures After(Test) hooks execute before test instance disposal
3. Bug Fixes: General stability improvements

🎯 Recommendations

1. ✅ Safe to merge - This is a routine dependency update with beneficial fixes
2. Consider running tests - While not strictly necessary for version bumps, running the snapshot tests would provide extra confidence
3. Monitor CI - Let the automated tests validate the changes
4. Auto-merge enabled - Renovate's auto-merge is appropriate for this type of update

---