chore(deps): update dependency benchmarkdotnet to 0.15.3

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
BenchmarkDotNet	nuget	patch	0.15.2 -> 0.15.3

---

Release Notes

dotnet/BenchmarkDotNet (BenchmarkDotNet)

v0.15.3: 0.15.3

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

Highlights

Improvements:

• Naot instruction set support for .NET 10+, migrate to ISA groupings in CPU summary #​2828
• Support benchmark filtering for TestAdapter #​2662 #​2788
• Support non-primitive external types in ArgumentsSource #​2820
• Disable MSBuild parallel build via --nodeReuse:false #​2693 #​2814
• Improve CPU detection #​2747 #​2749
• Enable assembly signing for debug build #​2774

Deprecations:

• Deprecated WithNuget #​2812

Bug fixes:

• Fix InvalidOperationException in diagnosers #​2758 #​2805
• Fix file detection in NativeMemoryProfiler #​2794 #​2795
• Fix long file paths issue in EtwProfiler #​2807 #​2808
• Fix log duplications in TestAdapter #​2790
• Fix x86 disassembler error for net462 #​2792
• Fix IsNetCore and IsNativeAOT for single-file apps without AOT #​2799
• Fix density plot generation in RPlotExporter for latest version of R #​2809

---

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 Dependency Update

Todo List:

• Read the changed file to understand the scope
• Analyze the BenchmarkDotNet changelog for breaking changes
• Check for security implications
• Assess performance considerations
• Verify compatibility with TUnit
• Provide comprehensive review feedback

Review Summary

This PR updates BenchmarkDotNet from version 0.15.2 to 0.15.3, which is a patch release containing bug fixes and improvements. The change is minimal and low-risk.

✅ Code Quality and Best Practices

• Clean change: Only updates the version number in Directory.Packages.props:10
• Centralized dependency management: Correctly uses centralized package management
• Consistent versioning approach: Follows semantic versioning principles

⚠️ Potential Issue Identified

Version Mismatch: I noticed that BenchmarkDotNet.Annotations remains at version 0.15.2 (line 11) while the main BenchmarkDotNet package is being updated to 0.15.3. This could potentially cause compatibility issues, though they're typically minor for patch releases.

Recommendation: Consider updating BenchmarkDotNet.Annotations to 0.15.3 as well to maintain version consistency.

✅ Security Considerations

• No security vulnerabilities: The 0.15.3 release notes don't mention any security fixes
• Low security impact: This is a development/testing dependency, not a runtime dependency in production
• Trusted source: BenchmarkDotNet is a well-maintained Microsoft-backed project

✅ Performance Considerations

Improvements in 0.15.3:

• Enhanced CPU detection (better hardware profiling)
• MSBuild parallel build optimizations with --nodeReuse:false
• Fixed diagnoser issues that could affect measurement accuracy
• Better NativeAOT instruction set support for .NET 10+

These changes should provide better benchmark accuracy and improved performance measurement for TUnit's performance tests.

✅ Test Coverage and Compatibility

TUnit Usage: The project uses BenchmarkDotNet extensively in:

• TUnit.Performance.Tests/ - Performance benchmarks for TUnit itself
• tools/speed-comparison/Tests.Benchmark/ - Framework comparison benchmarks

Compatibility:

• ✅ No breaking changes in this patch release
• ✅ All existing benchmark attributes and APIs remain compatible
• ✅ The code uses standard BenchmarkDotNet features that are stable across patch versions

📋 Changelog Highlights (0.15.3)

Improvements that benefit TUnit:

• Better CPU detection and ISA groupings
• TestAdapter filtering support
• Improved MSBuild performance
• Enhanced diagnoser stability

Bug fixes:

• Fixed InvalidOperationException in diagnosers
• Fixed file detection issues in NativeMemoryProfiler
• Fixed long file paths in EtwProfiler
• Fixed log duplications in TestAdapter

✅ Final Recommendation

APPROVE - This is a safe, beneficial update that:

• Fixes several bugs that could improve benchmark reliability
• Adds performance improvements to the benchmarking process
• Contains no breaking changes
• Aligns with TUnit's emphasis on performance testing

Minor suggestion: Update BenchmarkDotNet.Annotations to 0.15.3 for version consistency.

[claude]

Claude finished @thomhurst's task —— View job

---

PR Review: BenchmarkDotNet Dependency Update

Todo List:

• Read the changed file to understand the scope
• Analyze the BenchmarkDotNet changelog for breaking changes
• Check for security implications
• Assess performance considerations
• Verify compatibility with TUnit
• Provide comprehensive review feedback

Review Summary

This PR updates BenchmarkDotNet from version 0.15.2 to 0.15.3, which is a patch release containing bug fixes and improvements. The change affects the centralized package management in Directory.Packages.props:10-11.

✅ Code Quality and Best Practices

• Clean change: Updates both BenchmarkDotNet and BenchmarkDotNet.Annotations to 0.15.3 consistently
• Centralized dependency management: Correctly uses centralized package management via Directory.Packages.props
• Consistent versioning: Both packages are kept in sync, which is the correct approach

✅ Security Considerations

• No security vulnerabilities: The 0.15.3 release notes don't mention any security fixes
• Low security impact: This is a development/testing dependency used for performance benchmarking, not a runtime dependency in production
• Trusted source: BenchmarkDotNet is a well-maintained Microsoft-backed project

✅ Performance Considerations

Improvements in 0.15.3 that benefit TUnit:

• Enhanced CPU detection (better hardware profiling accuracy)
• MSBuild parallel build optimizations with --nodeReuse:false
• Fixed diagnoser issues that could affect measurement accuracy (InvalidOperationException fixes)
• Better NativeAOT instruction set support for .NET 10+ (relevant since TUnit.Performance.Tests uses PublishAot>true)

These changes should provide better benchmark accuracy and improved performance measurement for TUnit's performance tests.

✅ Test Coverage and Compatibility

TUnit's BenchmarkDotNet Usage: The project uses BenchmarkDotNet extensively in:

• TUnit.Performance.Tests/ - Performance benchmarks for TUnit itself (lines 13-14 in csproj)
• tools/speed-comparison/Tests.Benchmark/ - Framework comparison benchmarks (line 11 in csproj)

Compatibility Assessment:

• ✅ No breaking changes in this patch release
• ✅ All existing benchmark attributes and APIs remain compatible
• ✅ Standard BenchmarkDotNet usage patterns - Uses BenchmarkRunner.Run<T>() and BenchmarkSwitcher.FromAssembly()
• ✅ AOT compatibility maintained - Important since TUnit.Performance.Tests has PublishAot>true

📋 Changelog Highlights (0.15.3)

Bug fixes that improve benchmark reliability:

• Fixed InvalidOperationException in diagnosers
• Fixed file detection issues in NativeMemoryProfiler
• Fixed long file paths in EtwProfiler
• Fixed log duplications in TestAdapter

Performance improvements:

• Disabled MSBuild parallel build via --nodeReuse:false
• Improved CPU detection and ISA groupings
• Support for benchmark filtering in TestAdapter

✅ Final Recommendation

APPROVE - This is a safe, beneficial update that:

• ✅ Fixes several bugs that improve benchmark reliability and accuracy
• ✅ Adds performance improvements to the benchmarking process itself
• ✅ Contains no breaking changes
• ✅ Aligns with TUnit's emphasis on performance testing and measurement
• ✅ Maintains compatibility with existing benchmark code
• ✅ Both packages updated consistently to avoid version conflicts

The update is particularly valuable for TUnit given its focus on performance and the fact that it uses BenchmarkDotNet for both internal performance testing and framework comparison benchmarks.

---