chore(deps): update tunit to 1.6.0

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
TUnit	nuget	minor	1.5.80 → 1.6.0
TUnit.Assertions	nuget	minor	1.5.80 → 1.6.0
TUnit.Assertions.FSharp	nuget	minor	1.5.80 → 1.6.0
TUnit.Core	nuget	minor	1.5.80 → 1.6.0
TUnit.Playwright	nuget	minor	1.5.80 → 1.6.0

---

Release Notes

thomhurst/TUnit (TUnit)

v1.6.0: 1.6.0

What's Changed

Other Changes

• feat: TUnit.AspNetCore by @​thomhurst in #​4123

Dependencies

• chore(deps): update tunit to 1.5.80 by @​thomhurst in #​4111
• chore(deps): update dependency nunit3testadapter to 6.0.1 by @​thomhurst in #​4119

Full Changelog: v1.5.80...v1.6.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.

[claude]

Pull Request Review: TUnit 1.6.0 Dependency Update

Overview

This PR updates TUnit packages from 1.5.80 to 1.6.0 across template files and central package management. The update is generated by Renovate Bot and includes a minor version bump.

---

✅ Positive Observations

1. Consistent Version Updates: All TUnit-related packages are updated uniformly across:

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

2. Centralized Management: The Directory.Packages.props file correctly updates versions in one location, which will propagate to all projects using Central Package Management.

3. Template Consistency: All template project files (.csproj, .fsproj, .vbproj) are updated to reference the new version, ensuring users creating new projects from templates will use the latest version.

4. Clean Diff: The changes are surgical and only touch version numbers - no unintended modifications.

5. Automerge Enabled: Appropriate for automated dependency updates with proper CI validation.

---

📝 Considerations

1. Release Notes Context: According to the PR description, v1.6.0 introduces:

   • TUnit.AspNetCore (new feature from PR feat: TUnit.AspNetCore #4123)
   • This is a minor version bump, indicating backward-compatible new functionality

2. Testing Verification: Since this is a self-referential update (TUnit updating its own TUnit dependencies for templates), ensure:

   • Template generation tests pass
   • Integration tests with the new version work correctly
   • The new TUnit.AspNetCore package doesn't introduce breaking changes to existing templates

3. Missing Package: The PR updates references to TUnit.Playwright in templates, but Directory.Packages.props doesn't show a TUnit.Playwright entry (lines 88-91 show TUnit, TUnit.Core, TUnit.Assertions). This might be intentional if Playwright is managed separately, but worth verifying.

---

🔍 Code Quality Assessment

Style Compliance: ✅ No code changes to review
Breaking Changes: ❌ None expected (minor version bump)
Security Concerns: ❌ None identified
Performance Impact: ❌ None expected (dependency version only)

---

✅ Recommendation

APPROVE with minor verification

This PR is safe to merge once CI passes. The automated dependency update is well-structured and maintains consistency across all template files.

Suggested Pre-Merge Checklist:

• ✅ All CI checks pass (GitHub Actions, builds)
• ✅ Template generation tests succeed
• ⚠️ Verify TUnit.Playwright version management (if applicable)
• ✅ Renovate Bot's automerge is configured correctly

---

Review Completed: 2025-12-21
Reviewer: Claude (Automated PR Review)
Confidence Level: High (straightforward dependency update)

[Copilot]

Pull request overview

This PR updates TUnit packages from version 1.5.80 to 1.6.0 across all project templates and the central package management file. The update is a minor version bump that includes the new TUnit.AspNetCore feature according to the release notes. All package references are consistently updated without any breaking changes.

Key Changes:

• Updated TUnit core packages (TUnit, TUnit.Core, TUnit.Assertions) from 1.5.80 to 1.6.0
• Updated TUnit.Playwright and TUnit.Assertions.FSharp from 1.5.80 to 1.6.0
• Maintained consistency across all template projects and central package management

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
TUnit.Templates/content/TUnit/TestProject.csproj	Updated TUnit package reference to 1.6.0 in C# template
TUnit.Templates/content/TUnit.VB/TestProject.vbproj	Updated TUnit package reference to 1.6.0 in VB template
TUnit.Templates/content/TUnit.Playwright/TestProject.csproj	Updated TUnit.Playwright package reference to 1.6.0 in Playwright template
TUnit.Templates/content/TUnit.FSharp/TestProject.fsproj	Updated TUnit and TUnit.Assertions.FSharp package references to 1.6.0 in F# template
TUnit.Templates/content/TUnit.Aspire.Test/ExampleNamespace.csproj	Updated TUnit package reference to 1.6.0 in Aspire test template
TUnit.Templates/content/TUnit.Aspire.Starter/ExampleNamespace.TestProject/ExampleNamespace.TestProject.csproj	Updated TUnit package reference to 1.6.0 in Aspire starter template
TUnit.Templates/content/TUnit.AspNet/TestProject/TestProject.csproj	Updated TUnit package reference to 1.6.0 in ASP.NET template
TUnit.Templates/content/TUnit.AspNet.FSharp/TestProject/TestProject.fsproj	Updated TUnit and TUnit.Assertions.FSharp package references to 1.6.0 in ASP.NET F# template
Directory.Packages.props	Updated TUnit, TUnit.Core, and TUnit.Assertions package versions to 1.6.0 in central package management

---

Review Result: No issues found. This is a clean dependency update with consistent version bumps across all affected packages and templates.