chore(deps): update opentelemetry to 1.13.0

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
OpenTelemetry.Instrumentation.AspNetCore (source)	nuget	minor	1.12.0 -> 1.13.0
OpenTelemetry.Instrumentation.Http (source)	nuget	minor	1.12.0 -> 1.13.0
OpenTelemetry.Instrumentation.Runtime (source)	nuget	minor	1.12.0 -> 1.13.0

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled because a matching PR was automerged previously.

♻ 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

---

PR Review: OpenTelemetry Dependency Update

Todo List:

• Read project guidelines from CLAUDE.md
• Examine the changed .csproj file
• Analyze the OpenTelemetry version update
• Review for potential issues (bugs, security, performance)
• Assess test coverage implications
• Provide final review feedback

Review Summary: ✅ APPROVED

This is a clean, low-risk dependency update that should be safe to merge.

Detailed Analysis

Code Quality & Best Practices ✅

• Clean update: The changes are minimal and focused - only updating two OpenTelemetry instrumentation packages from 1.12.0 → 1.13.0
• Consistent versioning: The update maintains version consistency between related OpenTelemetry packages
• Template context: This affects only the Aspire starter template, limiting blast radius

Potential Bugs/Issues ✅ Low Risk

• Minor version update: This is a minor version bump (1.12.0 → 1.13.0), which should maintain backward compatibility according to semantic versioning
• Version alignment: Note that other OpenTelemetry packages in the file are already at newer versions:
  • OpenTelemetry.Exporter.OpenTelemetryProtocol: 1.13.1
  • OpenTelemetry.Extensions.Hosting: 1.13.1
  • OpenTelemetry.Instrumentation.Runtime: Still at 1.12.0 (not updated in this PR)

Performance Considerations ✅

• Template-only impact: Since this only affects the Aspire starter template (TUnit.Templates/content/TUnit.Aspire.Starter/), it won't impact TUnit's core performance
• OpenTelemetry overhead: These packages typically add minimal runtime overhead when properly configured
• Alignment with project goals: Per CLAUDE.md, TUnit prioritizes performance and this change doesn't affect core test execution paths

Security Concerns ✅

• Trusted source: OpenTelemetry is a CNCF project with strong security practices
• Patch updates: Minor version updates often include security fixes and improvements
• Dependency hygiene: Keeping dependencies current is a security best practice

Test Coverage ⚠️ Consideration Needed

• Template testing: This affects a project template, which may not be covered by TUnit's regular test suite
• Integration testing: Consider verifying that the Aspire starter template still builds and functions correctly
• Manual verification: Since this is a template, automated tests may not catch integration issues

Recommendations

1. ✅ Approve and merge: This is a safe dependency update
2. 🔍 Consider: Update OpenTelemetry.Instrumentation.Runtime to 1.13.0 in a follow-up for consistency
3. 🧪 Verify: Ensure the Aspire starter template builds successfully (though CI should catch this)

Risk Assessment: LOW 🟢

• Minor version update with backward compatibility expectations
• Limited to template code, not core TUnit functionality
• Well-maintained, trusted dependency

---

[claude]

Claude finished @thomhurst's task —— View job

---

PR Review: OpenTelemetry Dependency Update

Todo List:

• Read project guidelines from CLAUDE.md
• Examine the changed .csproj file
• Analyze the OpenTelemetry version update
• Review for potential issues (bugs, security, performance)
• Assess test coverage implications
• Provide final review feedback

Review Summary: ✅ APPROVED

This is a clean, low-risk dependency update that should be safe to merge.

Detailed Analysis

Code Quality & Best Practices ✅

• Clean update: The changes are minimal and focused - only updating three OpenTelemetry instrumentation packages from 1.12.0 → 1.13.0
• Consistent versioning: The update maintains version consistency between related OpenTelemetry packages
• Template context: This affects only the Aspire starter template, limiting blast radius

Potential Bugs/Issues ✅ Low Risk

• Minor version update: This is a minor version bump (1.12.0 → 1.13.0), which should maintain backward compatibility according to semantic versioning
• Version alignment: Good! The update brings these packages in line with other OpenTelemetry packages already at newer versions:
  • OpenTelemetry.Exporter.OpenTelemetryProtocol: 1.13.1
  • OpenTelemetry.Extensions.Hosting: 1.13.1
  • Now all instrumentation packages are at 1.13.0

Performance Considerations ✅

• Template-only impact: Since this only affects the Aspire starter template (TUnit.Templates/content/TUnit.Aspire.Starter/), it won't impact TUnit's core performance
• OpenTelemetry overhead: These packages typically add minimal runtime overhead when properly configured
• Alignment with project goals: Per CLAUDE.md, TUnit prioritizes performance and this change doesn't affect core test execution paths

Security Concerns ✅

• Trusted source: OpenTelemetry is a CNCF project with strong security practices
• Patch updates: Minor version updates often include security fixes and improvements
• Dependency hygiene: Keeping dependencies current is a security best practice

Test Coverage ⚠️ Consideration Needed

• Template testing: This affects a project template, which may not be covered by TUnit's regular test suite
• Integration testing: Consider verifying that the Aspire starter template still builds and functions correctly
• Manual verification: Since this is a template, automated tests may not catch integration issues

Recommendations

1. ✅ Approve and merge: This is a safe dependency update
2. 🔍 Consider: All OpenTelemetry packages are now properly aligned at compatible versions
3. 🧪 Verify: Ensure the Aspire starter template builds successfully (though CI should catch this)

Risk Assessment: LOW 🟢

• Minor version update with backward compatibility expectations
• Limited to template code, not core TUnit functionality
• Well-maintained, trusted dependency
• Brings version consistency across OpenTelemetry packages

---