chore(deps): update tunit to 1.6.20

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
TUnit	nuget	patch	1.6.15 → 1.6.20
TUnit.AspNetCore	nuget	patch	1.6.15 → 1.6.20
TUnit.Assertions	nuget	patch	1.6.15 → 1.6.20
TUnit.Assertions.FSharp	nuget	patch	1.6.15 → 1.6.20
TUnit.Core	nuget	patch	1.6.15 → 1.6.20
TUnit.Playwright	nuget	patch	1.6.15 → 1.6.20

---

Release Notes

thomhurst/TUnit (TUnit)

v1.6.20: 1.6.20

What's Changed

Other Changes

• feat: enhance assertion exception messages to include inline 'because' reasons by @​thomhurst in #​4142
• feat: Fix MatrixMethod attribute ignored for enum parameter type by @​thomhurst in #​4146

Dependencies

• chore(deps): update tunit to 1.6.15 by @​thomhurst in #​4143

Full Changelog: v1.6.15...v1.6.20

---

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]

PR Review: TUnit Package Update to 1.6.20

Summary

This is an automated Renovate PR updating TUnit packages from version 1.6.15 to 1.6.20 across the repository's central package management and template files.

---

✅ Code Quality

Excellent: The changes are clean, consistent, and follow the repository's centralized package management pattern:

• Central version management in Directory.Packages.props
• Consistent updates across all template files
• No code changes, only dependency version bumps

---

✅ Correctness

No Issues Found:

• All package references are updated atomically (1.6.15 → 1.6.20)
• No partial updates that could cause version mismatches
• Both TUnit and TUnit.Assertions.FSharp updated together in F# templates (maintains compatibility)
• The update includes packages: TUnit, TUnit.AspNetCore, TUnit.Core, TUnit.Assertions, TUnit.Playwright

According to the release notes, v1.6.20 includes:

• Enhanced assertion exception messages with inline 'because' reasons (feat: enhance assertion exception messages to include inline 'because' reasons #4142)
• Fix for MatrixMethod attribute being ignored for enum parameter types (feat: Fix MatrixMethod attribute ignored for enum parameter type #4146)

Both changes are backward-compatible enhancements/fixes, making this a safe patch update.

---

✅ Performance Considerations

No Impact: This is a dependency version update only. The release notes indicate:

• Feature enhancement (better error messages)
• Bug fix (MatrixMethod with enums)

No performance regressions are mentioned or expected from these changes.

---

✅ Security Concerns

None:

• Patch version update within the same minor version (1.6.x)
• No security advisories associated with these versions
• Updates are from the same repository (self-dogfooding)

---

✅ Test Coverage

Appropriate:

• This PR updates template references, not runtime code
• The actual TUnit packages (1.6.20) have already been tested in their own PRs (feat: enhance assertion exception messages to include inline 'because' reasons #4142, feat: Fix MatrixMethod attribute ignored for enum parameter type #4146)
• CI will verify that templates still build correctly with the new versions

Note: Since this is updating the repository's own published packages, the changes in 1.6.20 have already passed through the full test suite including:

• Source generator snapshot tests
• Reflection mode tests
• Public API tests
• Dual-mode verification

---

📋 Suggestions

None required - This is a straightforward dependency update that follows best practices:

1. ✅ Uses centralized package management
2. ✅ Updates all references atomically
3. ✅ Patch version (safe, backward-compatible)
4. ✅ Automerge enabled (appropriate for patch updates)

---

🎯 Recommendation

APPROVE: This PR is safe to merge. It's a routine dependency update that:

• Updates TUnit's template scaffolding to reference the latest stable version
• Includes backward-compatible bug fixes and enhancements
• Follows the repository's established patterns
• Has automerge appropriately enabled for this type of change

The PR is well-structured and requires no changes.

---

Review conducted in accordance with CLAUDE.md guidelines

[Copilot]

Pull request overview

This PR updates TUnit package dependencies from version 1.6.15 to 1.6.20 across template files and the central package management configuration. The update brings enhancements to assertion exception messages and fixes for MatrixMethod attributes with enum parameters.

Key Changes:

• Updated TUnit core packages (TUnit, TUnit.Core, TUnit.Assertions, TUnit.AspNetCore) to version 1.6.20
• Updated TUnit.Playwright to version 1.6.20 in template files
• Updated version references in all project templates (C#, F#, VB, ASP.NET, Aspire, Playwright)

Reviewed changes

Copilot reviewed 9 out of 9 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
Directory.Packages.props	Central package version management - updated TUnit, TUnit.Core, TUnit.Assertions, and TUnit.AspNetCore to 1.6.20
TUnit.Templates/content/TUnit/TestProject.csproj	Updated TUnit package reference to 1.6.20 in basic C# template
TUnit.Templates/content/TUnit.VB/TestProject.vbproj	Updated TUnit package reference to 1.6.20 in VB.NET template
TUnit.Templates/content/TUnit.Playwright/TestProject.csproj	Updated TUnit.Playwright package reference to 1.6.20 in Playwright template
TUnit.Templates/content/TUnit.FSharp/TestProject.fsproj	Updated TUnit and TUnit.Assertions.FSharp package references to 1.6.20 in F# template
TUnit.Templates/content/TUnit.Aspire.Test/ExampleNamespace.csproj	Updated TUnit package reference to 1.6.20 in Aspire test template
TUnit.Templates/content/TUnit.Aspire.Starter/ExampleNamespace.TestProject/ExampleNamespace.TestProject.csproj	Updated TUnit package reference to 1.6.20 in Aspire starter template
TUnit.Templates/content/TUnit.AspNet/TestProject/TestProject.csproj	Updated TUnit package reference to 1.6.20 in ASP.NET C# template
TUnit.Templates/content/TUnit.AspNet.FSharp/TestProject/TestProject.fsproj	Updated TUnit and TUnit.Assertions.FSharp package references to 1.6.20 in ASP.NET F# template

The changes are consistent and appropriate for a dependency update. All version numbers have been updated correctly across the codebase. No issues were identified with this straightforward dependency update PR.

[claude]

Pull Request Review - TUnit Version Update (1.6.15 → 1.6.20)

Summary

This is a Renovate-generated PR that bumps TUnit package versions from 1.6.15 to 1.6.20 across the codebase. The changes are straightforward and consistent.

✅ Positive Findings

1. Consistency

• All TUnit packages updated uniformly to 1.6.20
• Changes applied across all template files and Directory.Packages.props
• Version updates include: TUnit, TUnit.AspNetCore, TUnit.Core, TUnit.Assertions, TUnit.Assertions.FSharp, TUnit.Playwright

2. Scope

• Appropriate scope - only version numbers changed
• No code modifications, only dependency updates
• Follows centralized package management pattern (Directory.Packages.props)

3. Release Notes Review
The version jump includes:

• Enhancement to assertion exception messages with inline 'because' reasons (feat: enhance assertion exception messages to include inline 'because' reasons #4142)
• Fix for MatrixMethod attribute with enum parameters (feat: Fix MatrixMethod attribute ignored for enum parameter type #4146)
• These are patch-level improvements, appropriate for a 1.6.x update

📋 Observations

1. Template Consistency
All template project files correctly updated:

• ✅ TUnit.AspNet.FSharp
• ✅ TUnit.AspNet
• ✅ TUnit.Aspire.Starter
• ✅ TUnit.Aspire.Test
• ✅ TUnit.FSharp
• ✅ TUnit.Playwright
• ✅ TUnit.VB
• ✅ TUnit

2. No Breaking Changes
Patch version update (1.6.15 → 1.6.20) indicates no breaking changes expected.

🔍 Considerations

1. Automerge Enabled

• The PR has automerge enabled, which is appropriate for automated dependency updates
• Ensure CI checks pass before merge

2. Self-Referential Update

• This is TUnit updating its own TUnit dependencies (likely for templates/examples)
• Ensures templates reference the latest published versions

✅ Verdict

APPROVED - This is a clean, consistent dependency update with no concerns.

The changes are:

• ✅ Mechanically correct
• ✅ Consistently applied
• ✅ Appropriate scope (patch version)
• ✅ No code changes, only version bumps
• ✅ Follows repository conventions

Recommendation: Allow automerge to proceed once CI checks pass.

---

Review generated based on TUnit development guidelines from CLAUDE.md