[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
TUnit	nuget	minor	0.79.0 -> 0.80.0
TUnit.Assertions	nuget	minor	0.79.0 -> 0.80.0
TUnit.Assertions.FSharp	nuget	minor	0.79.0 -> 0.80.0
TUnit.Core	nuget	minor	0.79.0 -> 0.80.0
TUnit.Playwright	nuget	minor	0.79.0 -> 0.80.0

---

Release Notes

thomhurst/TUnit (TUnit)

v0.80.0: 0.80.0

What's Changed

🏕 Changes

• feat: refactor attribute handling to use a dictionary for better organization and access by @​thomhurst in #​3563
• fix: handle exceptions in ToString() for better argument formatting by @​thomhurst in #​3566
• Refactor test source generation to use deterministic filenames by @​thomhurst in #​3565

👒 Dependencies

• chore(deps): update tunit to 0.79.0 by @​thomhurst in #​3564

Full Changelog: v0.79.0...v0.80.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]

Claude finished @thomhurst's task —— View job

---

TUnit Dependency Update Review

Reviewing this dependency update from TUnit 0.79.0 to 0.80.0.

Todo List:

• Read repository guidelines (CLAUDE.md)
• Review changed files and scope
• Analyze release notes for breaking changes
• Check for potential issues
• Provide comprehensive feedback

Scope Analysis

This PR updates TUnit package versions from 0.79.0 to 0.80.0 in:

• Directory.Packages.props: Central package management (3 packages)
• Template projects: 8 template .csproj/.fsproj files across different scenarios
• No source code changes: Only version bumps

Packages updated:

• TUnit (core framework)
• TUnit.Core (abstractions)
• TUnit.Assertions (assertion library)
• TUnit.Assertions.FSharp (F# assertions)
• TUnit.Playwright (Playwright integration)

Release Notes Analysis (v0.80.0)

Changes included:

1. Attribute handling refactor - Better organization using dictionary-based access
2. Exception handling improvement - Better argument formatting in ToString()
3. Deterministic filename generation - More reliable source generation

Code Quality Assessment

✅ Positive Aspects:

• Clean dependency update: Only version number changes, no code modifications
• Self-dogfooding: This is TUnit updating its own dependencies in templates
• Consistent versioning: All TUnit packages updated to same version (0.80.0)
• Central package management: Uses Directory.Packages.props appropriately
• Minor version bump: Non-breaking semantic versioning

✅ Security:

• Low risk: No external dependencies or security-sensitive changes
• Trusted source: Internal TUnit packages from same repository
• Renovate Bot: Automated dependency management reduces human error

✅ Performance:

• Potential improvements: Release notes mention better attribute handling organization
• No performance regressions expected: Minor version with refactoring improvements

Potential Issues

⚠️ Minor Concerns:

• Template consistency: Need to ensure all template projects work with new version
• Snapshot tests: Changes to source generator may require snapshot updates per CLAUDE.md Rule 2

❌ No Breaking Changes Expected:

• Minor version bump (0.79.0 → 0.80.0) follows semantic versioning
• Release notes show internal improvements, not API changes
• Template projects should work without modification

Test Coverage Recommendation

Should run these tests before merge:

# Core functionality
dotnet test

# Source generator snapshots (due to deterministic filename changes)
dotnet test TUnit.Core.SourceGenerator.Tests

# Public API verification
dotnet test TUnit.PublicAPI

# Template validation
dotnet new tunit --name TestValidation
cd TestValidation && dotnet test

Final Recommendation

✅ APPROVED - This is a safe dependency update with the following rationale:

• Minor version bump with internal improvements only
• Clean version-only changes across template files
• Follows repository's package management conventions
• No API breaking changes indicated
• Automerge is appropriate for this type of update

Post-merge verification:

• CI should validate all template projects build and test successfully
• Any snapshot test failures should be reviewed and accepted if legitimate