chore(deps): update tunit to 1.0.27

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
TUnit	nuget	patch	1.0.0 -> 1.0.27
TUnit.Assertions	nuget	patch	1.0.0 -> 1.0.27
TUnit.Assertions.FSharp	nuget	patch	1.0.0 -> 1.0.27
TUnit.Core	nuget	patch	1.0.0 -> 1.0.27
TUnit.Playwright	nuget	patch	1.0.0 -> 1.0.27

---

Release Notes

thomhurst/TUnit (TUnit)

v1.0.27: 1.0.27

What's Changed

🏕 Changes

• Fix IsEquivalentTo documentation - remove non-existent IgnoringOrder method by @​Copilot in #​3718
• Add Benchmarks to Documentation Site by @​thomhurst in #​3719
• 🤖 Update Benchmark Results by @​github-actions[bot] in #​3720
• fix: Pass Items from TestBuilderContext StateBag to TestContext StateBag by @​thomhurst in #​3725

👒 Dependencies

• chore(deps): update tunit to v1 (major) by @​thomhurst in #​3710
• chore(deps): update dependency polyfill to 8.9.1 by @​thomhurst in #​3712
• chore(deps): update dependency polyfill to 8.9.1 by @​thomhurst in #​3713

Full Changelog: v1.0.0...v1.0.27

---

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 Dependency Update v1.0.0 → v1.0.27

Todo List

• Read and understand changed files
• Check repository guidelines (CLAUDE.md)
• Analyze version update scope and release notes
• Review for code quality and best practices
• Check for potential bugs or issues
• Evaluate performance considerations
• Assess security concerns
• Review test coverage implications
• Provide comprehensive feedback

---

Summary

This is a Renovate Bot automated dependency update that bumps 5 TUnit packages from 1.0.0 to 1.0.27 across template project files. The update is a patch version increment with 27 releases of improvements and bug fixes.

Code Quality & Best Practices ✅

Positive aspects:

• Central package management: Uses Directory.Packages.props for version management, ensuring consistency
• Consistent versioning: All TUnit packages updated to the same version (1.0.27)
• Template consistency: Updates applied uniformly across all template projects
• Modern project structure: All projects use SDK-style project files

Potential Issues & Bugs ⚠️

Low risk concerns:

1. Large version jump: 27 releases (1.0.0 → 1.0.27) is significant for a new major version
2. Release notes highlight a critical fix: v1.0.27 includes "fix: Pass Items from TestBuilderContext StateBag to TestContext StateBag" (fix: Pass Items from TestBuilderContext StateBag to TestContext StateBag #3725) - this suggests data flow issues that could have affected test execution
3. No verification testing: Can't verify compatibility without running tests (requires approval for dotnet test)

Performance Considerations ✅

From release notes analysis:

• v1.0.27 includes benchmark additions to documentation site
• The StateBag fix likely improves performance by ensuring proper data flow
• No performance regressions mentioned in release notes
• Template projects are lightweight and unlikely to be affected by performance changes

Security Concerns ✅

Security assessment:

• Low risk: This is a patch update within the same major version
• Trusted source: TUnit is maintained by the same organization (thomhurst)
• No new dependencies: Only version bumps, no new package references
• Template scope: Changes only affect template projects used for scaffolding new projects

Test Coverage Implications ⚠️

Considerations:

1. StateBag fix: The key fix in v1.0.27 addresses test context data passing - this could affect test execution behavior
2. Template testing: Templates should be tested to ensure they scaffold correctly with new versions
3. Dual-mode compatibility: Per repository guidelines, both source-generated and reflection modes must work identically

Recommendations

✅ APPROVE - with conditions:

1. Run full test suite: Execute dotnet test to verify no regressions
2. Test template scaffolding: Verify template projects can be created and run successfully
3. Monitor for issues: The StateBag fix suggests there were data flow problems - watch for related issues

📋 Verification steps (should be automated in CI):

# Test core functionality
dotnet test TUnit.Engine.Tests
dotnet test TUnit.Assertions.Tests  
dotnet test TUnit.Core.SourceGenerator.Tests

# Verify template functionality
cd TUnit.Templates && dotnet test

# Check for snapshot updates if needed
dotnet test TUnit.PublicAPI

Risk Assessment: LOW 🟢

• Patch version update within established major version
• Automated dependency management by trusted bot
• Changes limited to template files
• Critical bug fix included (StateBag data passing)
• No breaking changes expected

Conclusion

This dependency update is well-structured and safe to merge after verification testing. The StateBag fix in v1.0.27 appears to address a legitimate issue with test context data flow, making this a beneficial update.

Final recommendation: Approve and merge after CI passes.