chore(deps): update dependency benchmarkdotnet to 0.15.8

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
BenchmarkDotNet	nuget	patch	0.15.7 -> 0.15.8

---

Release Notes

dotnet/BenchmarkDotNet (BenchmarkDotNet)

v0.15.8: BenchmarkDotNet v0.15.8

Full changelog: https://benchmarkdotnet.org/changelog/v0.15.8.html

---

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 this update 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

---

PR Review: BenchmarkDotNet Update 0.15.7 → 0.15.8

Todo List:

• Read the changed file (Directory.Packages.props)
• Analyze the dependency update for potential issues
• Check for benchmark-related code in the codebase
• Review BenchmarkDotNet 0.15.8 changes
• Provide comprehensive review feedback

📋 Review Summary

✅ Approved - Safe Dependency Update

This is a straightforward patch version update with minimal risk. The change updates BenchmarkDotNet from 0.15.7 to 0.15.8, which according to semantic versioning should contain only bug fixes and non-breaking changes.

---

📁 Code Quality & Changes

Changed Files:

• Directory.Packages.props:10 - BenchmarkDotNet version bump

Impact Assessment:

• TUnit.Performance.Tests - Performance benchmarking suite ✅
• tools/speed-comparison/Tests.Benchmark - Framework comparison benchmarks ✅
• Both projects use central package management via PackageReference without explicit versions

---

🐛 Potential Issues

⚠️ Version Mismatch Detected

<PackageVersion Include="BenchmarkDotNet" Version="0.15.8" />           
<PackageVersion Include="BenchmarkDotNet.Annotations" Version="0.15.7" /> 

Recommendation: Update BenchmarkDotNet.Annotations to 0.15.8 for consistency. Version mismatches between related packages can cause:

• Runtime compatibility issues
• Inconsistent attribute behavior
• Potential assembly resolution conflicts

---

🚀 Performance Considerations

Low Risk: Patch updates typically include:

• Performance improvements
• Bug fixes
• Internal optimizations

No Breaking Changes Expected: Semantic versioning guarantees backward compatibility for patch releases.

---

🔒 Security Concerns

None Identified: BenchmarkDotNet is a well-maintained Microsoft-affiliated project with regular security updates. Patch updates often include security fixes.

---

🧪 Test Coverage

Existing Coverage:

• Performance benchmarks in TUnit.Performance.Tests/
• Comparative benchmarks in tools/speed-comparison/
• Tests should continue to pass without modification

Recommendation: Run the benchmark suite after merge to ensure compatibility:

cd TUnit.Performance.Tests
dotnet run -c Release

---

📝 Final Recommendation

✅ APPROVE with suggestion to also update BenchmarkDotNet.Annotations to 0.15.8 for version consistency.

Why this is safe:

1. Patch version update (0.15.7 → 0.15.8)
2. No breaking changes expected
3. Well-maintained package with regular updates
4. Existing test coverage will validate compatibility

---

[claude]

Claude finished @thomhurst's task —— View job

---

PR Review: BenchmarkDotNet Update 0.15.7 → 0.15.8

Todo List:

• Read the changed file (Directory.Packages.props)
• Analyze the dependency update for potential issues
• Check for benchmark-related code in the codebase
• Review BenchmarkDotNet 0.15.8 changes
• Provide comprehensive review feedback

📋 Review Summary

✅ Approved - Safe Dependency Update

This is a straightforward patch version update with minimal risk. The change updates both BenchmarkDotNet and BenchmarkDotNet.Annotations from 0.15.7 to 0.15.8, addressing the version consistency issue identified in previous reviews.

---

📁 Code Quality & Changes

Changed Files:

• Directory.Packages.props:10 - BenchmarkDotNet version bump to 0.15.8
• Directory.Packages.props:11 - BenchmarkDotNet.Annotations version bump to 0.15.8

Impact Assessment:

• TUnit.Performance.Tests ✅ - Performance benchmarking suite using BenchmarkDotNet attributes and runtime configurations
• tools/speed-comparison/Tests.Benchmark ✅ - Framework comparison benchmarks with custom BenchmarkConfig
• Both projects use central package management via PackageReference without explicit versions
• Extensive benchmark infrastructure including AOT compatibility (PublishAot=true)

---

🐛 Potential Issues

✅ Version Consistency - RESOLVED

Previous concern about BenchmarkDotNet.Annotations being at 0.15.7 while BenchmarkDotNet was at 0.15.8 has been resolved in this PR. Both packages are now consistently at 0.15.8.

🔍 Compatibility Assessment

• Benchmark Attributes: Standard usage of [Benchmark], [GlobalSetup], [SimpleJob], [MemoryDiagnoser] - no breaking changes expected
• Configuration API: Custom BenchmarkConfig using standard APIs (Jobs, Exporters, Columns) - stable interfaces
• Runtime Targets: Using RuntimeMoniker.Net80 and RuntimeMoniker.NativeAot80 - well-established enums

---

🚀 Performance Considerations

Low Risk: Patch updates (0.15.7 → 0.15.8) typically include:

• Bug fixes and stability improvements
• Performance optimizations
• Internal refactoring without API changes

Benchmark-Specific Benefits:

• Potential improvements to measurement accuracy
• Enhanced AOT compatibility (important for TUnit.Performance.Tests with PublishAot=true)
• Bug fixes in result collection or export functionality

---

🔒 Security Concerns

None Identified: BenchmarkDotNet is:

• A well-maintained Microsoft-affiliated project
• Actively developed with regular security updates
• Used only in development/testing contexts (not production runtime)
• Patch updates often include security fixes

---

🧪 Test Coverage

Existing Coverage:

• Performance benchmarks in TUnit.Performance.Tests/ covering test discovery, execution, and data sources
• Comparative framework benchmarks in tools/speed-comparison/
• Automated benchmark workflows in .github/workflows/speed-comparison.yml

Validation Strategy:

# Verify benchmark functionality after update
cd TUnit.Performance.Tests && dotnet run -c Release
cd tools/speed-comparison/Tests.Benchmark && dotnet run -c Release

Expected Outcome: All existing benchmarks should continue to function identically with potentially improved performance or accuracy.

---

💡 Additional Observations

Positive Implementation Details:

• ✅ Central package management through Directory.Packages.props
• ✅ Consistent versioning across related packages
• ✅ AOT-compatible benchmark setup
• ✅ Comprehensive benchmark coverage (discovery, execution, comparison)
• ✅ Professional benchmark configuration with proper job definitions

No Action Required:

• Update maintains semantic versioning compatibility
• No manual intervention needed for existing benchmark code
• Automerge configuration is appropriate for this low-risk change

---

📝 Final Recommendation

✅ APPROVE - This is a safe, well-executed dependency update.

Why this is safe:

1. ✅ Patch version update (0.15.7 → 0.15.8) with no breaking changes
2. ✅ Version consistency maintained between BenchmarkDotNet packages
3. ✅ Well-maintained package with regular updates
4. ✅ Comprehensive existing test coverage validates compatibility
5. ✅ Proper central package management implementation
6. ✅ AOT-compatible configuration preserved

Next Steps:

• ✅ Automerge can proceed safely
• 📊 Monitor post-merge benchmark runs for any performance changes (though none expected)

---