chore(deps): update tunit to 1.5.60

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
TUnit	nuget	patch	1.5.53 -> 1.5.60
TUnit.Assertions	nuget	patch	1.5.53 -> 1.5.60
TUnit.Assertions.FSharp	nuget	patch	1.5.53 -> 1.5.60
TUnit.Core	nuget	patch	1.5.53 -> 1.5.60
TUnit.Playwright	nuget	patch	1.5.53 -> 1.5.60

---

Release Notes

thomhurst/TUnit (TUnit)

v1.5.60: 1.5.60

What's Changed

Other Changes

• Add Claude Code GitHub Workflow by @​thomhurst in #​4067
• Add documentation for test artifacts/attachments by @​Copilot in #​4074
• docs: add test lifecycle overview and update sidebar by @​thomhurst in #​4077
• feat: add simple overload for attaching artifacts with optional display name and description by @​thomhurst in #​4078

Dependencies

• chore(deps): update tunit to 1.5.53 by @​thomhurst in #​4069

Full Changelog: v1.5.53...v1.5.60

---

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]

Code Review: TUnit Dependency Update (1.5.53 → 1.5.60)

Summary

This PR updates TUnit packages from version 1.5.53 to 1.5.60 across templates and the central package management file. This is a standard Renovate-generated dependency update.

---

✅ Positive Observations

1. Consistent Updates: All TUnit package references are updated consistently across:

   • Directory.Packages.props (central package management)
   • Multiple template project files (C#, F#, VB, Playwright, AspNet, Aspire)

2. Proper Central Package Management: The PR correctly updates the Directory.Packages.props file, which is the source of truth for package versions in this repository.

3. Template Consistency: All 9 template files are updated in sync, maintaining consistency across different project types.

4. Clean Diff: The changes are minimal and focused - only version number updates with no unrelated changes.

---

⚠️ Issue Found: Missing TUnit.Playwright in Central Package Management

Problem: Directory.Packages.props is missing a TUnit.Playwright package version entry.

Evidence:

• The template file TUnit.Templates/content/TUnit.Playwright/TestProject.csproj references:

  <PackageReference Include="TUnit.Playwright" Version="1.5.60" />

• But Directory.Packages.props only defines:

  <PackageVersion Include="TUnit" Version="1.5.60" />
  <PackageVersion Include="TUnit.Core" Version="1.5.60" />
  <PackageVersion Include="TUnit.Assertions" Version="1.5.60" />
  <!-- TUnit.Playwright is MISSING -->

Impact:

• This inconsistency means the Playwright template is not using centralized package management properly
• Future updates might miss the Playwright package
• This violates the repository's central package management pattern

Recommendation: Add the following line to Directory.Packages.props:

<PackageVersion Include="TUnit.Playwright" Version="1.5.60" />

And update the template to reference it without a hardcoded version (if using central package management pattern).

---

📋 Additional Observations

1. TUnit.Assertions.FSharp: This package is defined in Directory.Packages.props but uses a different version pattern (0.75.38-PullRequest3485.0) compared to other TUnit packages. This appears intentional (possibly testing a PR version).

2. Test Coverage: Since this is a dependency update affecting templates, ensure that:

   • Template instantiation tests pass ✅
   • The updated versions are compatible with the codebase ✅
   • Snapshot tests for templates are updated if needed ✅

3. Version Jump: The update from 1.5.53 to 1.5.60 includes 7 patch versions. According to the PR description, these include:

   • Documentation updates
   • Feature additions (artifact attachment overload)
   • Other dependency updates

   All changes appear to be non-breaking patch updates. ✅

---

🎯 Verdict

Overall: The PR is well-structured and follows proper dependency update practices, but has one gap in central package management.

Recommendation:

1. ✅ Approve the current changes (they are correct and consistent)
2. ⚠️ Follow-up: Add TUnit.Playwright to Directory.Packages.props in a separate PR or this one

Priority: Low - The current implementation works, but adding central package management for TUnit.Playwright would improve consistency and maintainability.

---

🤖 Review Notes

This review was performed according to TUnit's CLAUDE.md guidelines, focusing on:

• Code consistency and best practices ✅
• Central package management patterns ✅
• Template integrity ✅
• Version compatibility ✅

[Copilot]

Pull request overview

This PR updates the TUnit testing framework and related packages from version 1.5.53 to 1.5.60 across all project templates and central package management. This is a routine dependency maintenance update that brings in recent improvements including documentation enhancements, test lifecycle updates, and a new artifact attachment API.

Key Changes:

• Updated TUnit core packages to version 1.5.60
• Updated TUnit.Assertions and TUnit.Assertions.FSharp to version 1.5.60
• Updated TUnit.Playwright to version 1.5.60

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

---

Review Summary: No issues found. This is a clean dependency update with consistent version bumps across all affected files. All package references have been properly updated to version 1.5.60, and no old version references remain.

[claude]

PR Review: Dependency Update - TUnit 1.5.53 → 1.5.60

Summary

This is an automated dependency update by Renovate Bot that updates TUnit package references across the repository from version 1.5.53 to 1.5.60.

Code Quality ✅

Positive aspects:

• Clean, straightforward version bump across all package references
• Consistent update pattern across all files
• Both main Directory.Packages.props and template projects updated uniformly
• No breaking changes expected (patch version update)

Files Changed (9 files)

Main configuration:

• Directory.Packages.props: Core package versions (TUnit, TUnit.Core, TUnit.Assertions)

Template projects:

• TUnit.AspNet.FSharp, TUnit.AspNet, TUnit.Aspire.Starter, TUnit.Aspire.Test
• TUnit.FSharp, TUnit.Playwright, TUnit.VB, TUnit templates

Security & Stability 🔒

Low risk assessment:

• Patch version update (1.5.x → 1.5.x) suggests backward-compatible bug fixes
• All updates are internal to the TUnit ecosystem (dogfooding own packages)
• According to release notes, includes:
  • Documentation improvements
  • New artifact attachment overload (feat: simple overload for attaching artifacts)
  • No reported breaking changes

Recommendations 📋

Pre-merge verification:

1. ✅ Ensure CI/CD pipeline passes all tests
2. ✅ Verify template generation still works correctly
3. ✅ Confirm automerge is appropriate for this change

Observations:

• Since this updates the framework's own dependencies to itself, this is "dogfooding" which is good practice
• The templates consume the published versions, so these updates keep templates in sync with latest releases
• Renovate Bot has automerge enabled - appropriate for patch updates

Conclusion

APPROVED ✅

This is a clean, low-risk dependency update that:

• Maintains consistency across all project templates
• Updates to latest patch version with bug fixes and improvements
• Follows semantic versioning (patch = backward compatible)
• Aligns with automated dependency management best practices

No issues identified. Safe to merge once CI passes.

---

Reviewed by Claude Code - Following TUnit development guidelines from CLAUDE.md