chore(deps): update tunit to 0.77.0

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
TUnit	nuget	minor	0.76.26 -> 0.77.0
TUnit.Assertions	nuget	minor	0.76.26 -> 0.77.0
TUnit.Assertions.FSharp	nuget	minor	0.76.26 -> 0.77.0
TUnit.Core	nuget	minor	0.76.26 -> 0.77.0
TUnit.Playwright	nuget	minor	0.76.26 -> 0.77.0

---

Release Notes

thomhurst/TUnit (TUnit)

v0.77.0: 0.77.0

What's Changed

🏕 Changes

• refactor: adjust default max parallelism limit by @​thomhurst in #​3533

👒 Dependencies

• chore(deps): update tunit to 0.76.26 by @​thomhurst in #​3531

Full Changelog: v0.76.26...v0.77.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

---

Comprehensive Code Review

• Read repository guidelines (CLAUDE.md)
• Examine changed files and version updates
• Review release notes and changelog for 0.77.0
• Assess code quality and best practices
• Check for potential bugs or breaking changes
• Evaluate performance and security considerations
• Verify test coverage implications

Review Summary: ✅ APPROVED - Clean Dependency Update

This is a well-structured Renovate PR that updates TUnit packages from 0.76.26 to 0.77.0. The changes are minimal, consistent, and follow best practices.

📋 Changes Analyzed

Updated Packages:

• TUnit: 0.76.26 → 0.77.0
• TUnit.Core: 0.76.26 → 0.77.0
• TUnit.Assertions: 0.76.26 → 0.77.0
• TUnit.Playwright: 0.76.26 → 0.77.0 (in templates)
• TUnit.Assertions.FSharp: 0.76.26 → 0.77.0 (in templates)

Files Updated:

• Directory.Packages.props (central package management)
• 8 template project files across different TUnit project types

🔍 Code Quality & Best Practices ✅

• Excellent: Uses centralized package management via Directory.Packages.props
• Consistent: All template references updated uniformly
• Clean: No breaking changes to project structure or dependencies
• Modern: Follows .NET best practices with ImplicitUsings and Nullable enabled

🐛 Potential Issues ✅ None Found

• No breaking changes: Minor version bump (0.76.x → 0.77.0) indicates backward compatibility
• Template consistency: All templates properly updated to use new version
• No missing updates: All TUnit package references found and updated correctly

🚀 Performance Considerations ✅ Positive Impact

The key feature in 0.77.0 is enhanced parallelism configuration (PR #3533):

Performance Improvements:

• Smarter defaults: Now defaults to ProcessorCount * 4 instead of unlimited parallelism
• Better resource management: Prevents exhaustion of DB connections, memory, file handles
• Configurable limits: Supports both command-line args and environment variables
• I/O optimization: 4x multiplier allows I/O-bound tests to overlap effectively

Before (0.76.26):

// Default was unlimited (int.MaxValue) unless explicitly set
return int.MaxValue;

After (0.77.0):

// Smart default: 4x CPU cores, with priority hierarchy:
// 1. Command line argument (--maximum-parallel-tests)
// 2. Environment variable (TUNIT_MAX_PARALLEL_TESTS)
// 3. Default: ProcessorCount * 4
var defaultLimit = Environment.ProcessorCount * 4;

🔒 Security Concerns ✅ None

• Standard dependency update with no security implications
• No new attack vectors introduced
• Environment variable reading is safe (standard .NET API)

🧪 Test Coverage Impact ✅ Maintained

• No functional changes that require additional test coverage
• Template updates maintain existing test project structures
• The parallelism feature was already covered in the base TUnit codebase

⚠️ Minor Note

One inconsistency noticed in Directory.Packages.props:83:

<PackageVersion Include="TUnit.Assertions.FSharp" Version="0.75.38-PullRequest3485.0" />

This appears to be a pre-release version that wasn't updated. This seems intentional (likely for ongoing development) and doesn't affect this PR's scope.

🎯 Recommendation

✅ APPROVE and MERGE - This is a clean, beneficial dependency update that:

• Improves performance through smarter parallelism defaults
• Maintains backward compatibility
• Follows established project conventions
• Updates all relevant template references consistently

The new parallelism configuration will help prevent resource exhaustion issues while maintaining test execution speed.

---

[claude]

Claude finished @thomhurst's task —— View job

---

Comprehensive Code Review

• Read repository guidelines (CLAUDE.md)
• Examine changed files and version updates
• Review release notes and changelog for 0.77.0
• Assess code quality and best practices
• Check for potential bugs or breaking changes
• Evaluate performance and security considerations
• Verify test coverage implications

Review Summary: ✅ APPROVED - Clean Dependency Update

This is a well-structured Renovate PR that updates TUnit packages from 0.76.26 to 0.77.0. The changes are minimal, consistent, and follow best practices.

📋 Changes Analyzed

Updated Packages:

• TUnit: 0.76.26 → 0.77.0
• TUnit.Core: 0.76.26 → 0.77.0
• TUnit.Assertions: 0.76.26 → 0.77.0
• TUnit.Playwright: 0.76.26 → 0.77.0 (in templates)
• TUnit.Assertions.FSharp: 0.76.26 → 0.77.0 (in templates)

Files Updated:

• Directory.Packages.props (central package management)
• 8 template project files across different TUnit project types

🔍 Code Quality & Best Practices ✅

• Excellent: Uses centralized package management via Directory.Packages.props
• Consistent: All template references updated uniformly
• Clean: No breaking changes to project structure or dependencies
• Modern: Follows .NET best practices with ImplicitUsings and Nullable enabled

🐛 Potential Issues ✅ None Found

• No breaking changes: Minor version bump (0.76.x → 0.77.0) indicates backward compatibility
• Template consistency: All templates properly updated to use new version
• No missing updates: All TUnit package references found and updated correctly

🚀 Performance Considerations ✅ Positive Impact

The key feature in 0.77.0 is enhanced parallelism configuration (PR #3533):

Performance Improvements:

• Smarter defaults: Now defaults to ProcessorCount * 4 instead of unlimited parallelism
• Better resource management: Prevents exhaustion of DB connections, memory, file handles
• Configurable limits: Supports both command-line args and environment variables
• I/O optimization: 4x multiplier allows I/O-bound tests to overlap effectively

Before (0.76.26):

// Default was unlimited (int.MaxValue) unless explicitly set
return int.MaxValue;

After (0.77.0):

// Smart default: 4x CPU cores, with priority hierarchy:
// 1. Command line argument (--maximum-parallel-tests)
// 2. Environment variable (TUNIT_MAX_PARALLEL_TESTS)
// 3. Default: ProcessorCount * 4
var defaultLimit = Environment.ProcessorCount * 4;

🔒 Security Concerns ✅ None

• Standard dependency update with no security implications
• No new attack vectors introduced
• Environment variable reading is safe (standard .NET API)

🧪 Test Coverage Impact ✅ Maintained

• No functional changes that require additional test coverage
• Template updates maintain existing test project structures
• The parallelism feature was already covered in the base TUnit codebase

⚠️ Minor Note

One inconsistency noticed in Directory.Packages.props:83:

<PackageVersion Include="TUnit.Assertions.FSharp" Version="0.75.38-PullRequest3485.0" />

This appears to be a pre-release version that wasn't updated. This seems intentional (likely for ongoing development) and doesn't affect this PR's scope.

🎯 Recommendation

✅ APPROVE and MERGE - This is a clean, beneficial dependency update that:

• Improves performance through smarter parallelism defaults
• Maintains backward compatibility
• Follows established project conventions
• Updates all relevant template references consistently

The new parallelism configuration will help prevent resource exhaustion issues while maintaining test execution speed.

---