chore(deps): update tunit to 1.1.27

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
TUnit	nuget	patch	1.1.10 -> 1.1.27
TUnit.Assertions	nuget	patch	1.1.10 -> 1.1.27
TUnit.Assertions.FSharp	nuget	patch	1.1.10 -> 1.1.27
TUnit.Core	nuget	patch	1.1.10 -> 1.1.27
TUnit.Playwright	nuget	patch	1.1.10 -> 1.1.27

---

Release Notes

thomhurst/TUnit (TUnit)

v1.1.27: 1.1.27

What's Changed

🏕 Changes

• Fix documentation: Update TestContext API from context.Result to context.Execution.Result by @​Copilot in #​3837
• Clarify TUnit0046 diagnostic message for data source return types by @​Copilot in #​3843
• feat(tests): add timeout cancellation token tests and enhance test context by @​thomhurst in #​3838
• Optimize GetOrAdd method in ThreadSafeDictionary for improved concurrency handling by @​thomhurst in #​3845

👒 Dependencies

• chore(deps): update dependency microsoft.build.utilities.core to v18 by @​thomhurst in #​3817
• chore(deps): update dependency benchmarkdotnet to 0.15.7 by @​thomhurst in #​3818
• chore(deps): update dependency benchmarkdotnet.annotations to 0.15.7 by @​thomhurst in #​3819
• chore(deps): update tunit to 1.1.10 by @​thomhurst in #​3821
• chore(deps): update dependency polyfill to 9.0.2 by @​thomhurst in #​3823
• chore(deps): update dependency polyfill to 9.0.2 by @​thomhurst in #​3790
• chore(deps): update verify to 31.7.1 by @​thomhurst in #​3825
• chore(deps): update dependency polyfill to 9.0.3 by @​thomhurst in #​3840
• chore(deps): update dependency polyfill to 9.0.3 by @​thomhurst in #​3839

Full Changelog: v1.1.10...v1.1.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

---

Pull Request Review

Todo List:

• Examine changed files and version updates
• Analyze release notes for breaking changes or security issues
• Check for consistency across all template files
• Assess potential impact on users
• Provide comprehensive review feedback

---

Review Summary ✅

This is a clean and well-executed dependency update from Renovate. The PR updates TUnit packages from version 1.1.10 to 1.1.27 across all template files.

Code Quality & Best Practices ✅

• Consistent Updates: All TUnit packages are updated consistently to version 1.1.27 across all template project files
• Central Management: The updates are properly managed through Directory.Packages.props for centralized version control
• Template Synchronization: All 9 template files are updated consistently, maintaining uniformity across different project types (C#, F#, VB.NET, ASP.NET, Aspire, Playwright)

Security Considerations ✅

• Patch Release: This is a patch version update (1.1.10 → 1.1.27), indicating bug fixes and improvements without breaking changes
• No Security Vulnerabilities: The release notes show this update includes several fixes and optimizations without any security-related concerns
• Automated Update: Renovate bot ensures systematic and reliable dependency management

Performance Considerations ✅

• Performance Improvements: The release notes specifically mention "Optimize GetOrAdd method in ThreadSafeDictionary for improved concurrency handling" - this is a positive performance enhancement
• No Regressions: The changes are limited to version numbers only, with no code modifications that could introduce performance issues

Potential Issues ⚠️

• Missing TUnit.Playwright Update: I notice that in Directory.Packages.props (lines 86-88), only TUnit, TUnit.Core, and TUnit.Assertions are updated, but TUnit.Playwright is not explicitly listed. However, the template file correctly references TUnit.Playwright version 1.1.27, which should work correctly.

Test Coverage 📋

• No Test Changes Needed: Since this is purely a version bump with no breaking changes, existing tests should continue to pass
• Template Validation: The template projects serve as integration tests themselves

Recommendations ✅

1. Approve and Merge: This PR is safe to merge as it follows proper dependency update practices
2. Automerge Appropriate: The automerge configuration is appropriate for patch-level dependency updates
3. Monitor CI: Ensure all CI checks pass to validate the updates work correctly across all project templates

Changes Breakdown

• Directory.Packages.props: Updated 3 core TUnit package versions
• Template Files: Updated 6 different template project files consistently
• Coverage: All major TUnit packages and project templates are properly updated

This is an exemplary dependency update PR that maintains consistency, follows best practices, and provides clear value through bug fixes and performance improvements.

---