chore(deps): update dependency fsharp.core to 9.0.303

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
FSharp.Core	nuget	patch	9.0.300 -> 9.0.303

---

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: FSharp.Core Dependency Update

Todo List:

• Read repository guidelines (CLAUDE.md) - No CLAUDE.md found
• Analyze the changed file (Directory.Packages.props)
• Check for any breaking changes in FSharp.Core 9.0.303
• Assess security implications
• Evaluate test coverage needs
• Provide comprehensive review feedback

---

Review Summary ✅

This is a low-risk patch update that looks good to merge. Here's my detailed analysis:

Code Quality & Best Practices ✅

• Centralized Package Management: Properly using Directory.Packages.props for version management
• Single Responsibility: Clean, focused change updating only FSharp.Core version
• Semantic Versioning: Following proper patch version increment (9.0.300 → 9.0.303)

Potential Issues & Breaking Changes ✅

• Patch Version: This is a patch release, so no breaking changes expected
• F# Projects Impact: Found multiple F# projects in the codebase:
  • TUnit.TestProject.FSharp/ - Main F# test project
  • TUnit.Assertions.FSharp/ - F# assertions library
  • TUnit.Templates/content/TUnit.FSharp/ - F# project templates
  • Various other F# test and template projects
• Dependencies: All F# projects reference FSharp.Core via centralized package management at Directory.Packages.props:16

Security Considerations ✅

• Official Package: FSharp.Core is Microsoft's official F# runtime library
• Trusted Source: Updates come from Microsoft's official NuGet feed
• No Security Concerns: Patch versions typically contain bug fixes and performance improvements

Performance Considerations ✅

• Runtime Improvements: Patch updates often include performance optimizations
• No Degradation Expected: Patch versions maintain API compatibility and performance characteristics

Test Coverage Assessment ✅

• Existing Coverage: The codebase has comprehensive F# test projects that will validate the update
• No Additional Tests Needed: For a patch version dependency update, existing tests provide adequate coverage
• Automated Testing: The CI pipeline will validate all F# functionality works with the new version

Recommendations

1. ✅ Approve: This is a safe patch update from a trusted source
2. ✅ Auto-merge: Perfect candidate for Renovate's auto-merge feature
3. ✅ Monitor: CI tests will catch any unexpected issues

Note

Unable to run local build validation due to .NET SDK version mismatch (requires 9.0.302, GitHub Actions runner has 8.0.118), but the CI pipeline will handle this validation.

---

[claude]

Claude finished @thomhurst's task —— View job

---

PR Review: FSharp.Core Dependency Update

Todo List:

• Read repository guidelines (CLAUDE.md) - No CLAUDE.md found
• Analyze the changed file (Directory.Packages.props)
• Check for F# projects that would be affected
• Assess potential breaking changes in FSharp.Core 9.0.303
• Evaluate security implications
• Review performance considerations
• Assess test coverage needs
• Provide comprehensive review feedback

---

Review Summary ✅

This is a low-risk patch update that looks good to merge. Here's my detailed analysis:

Code Quality & Best Practices ✅

• Centralized Package Management: Properly using Directory.Packages.props for version management
• Single Responsibility: Clean, focused change updating only FSharp.Core version
• Semantic Versioning: Following proper patch version increment (9.0.300 → 9.0.303)

Potential Issues & Breaking Changes ✅

• Patch Version: This is a patch release, so no breaking changes expected
• F# Projects Impact: Found multiple F# projects in the codebase:
  • TUnit.TestProject.FSharp/ - Main F# test project
  • TUnit.Assertions.FSharp/ - F# assertions library
  • TUnit.Templates/content/TUnit.FSharp/ - F# project templates
  • Various other F# test and template projects
• Dependencies: All F# projects reference FSharp.Core via centralized package management at Directory.Packages.props:16

Security Considerations ✅

• Official Package: FSharp.Core is Microsoft's official F# runtime library
• Trusted Source: Updates come from Microsoft's official NuGet feed
• No Security Concerns: Patch versions typically contain bug fixes and performance improvements

Performance Considerations ✅

• Runtime Improvements: Patch updates often include performance optimizations
• No Degradation Expected: Patch versions maintain API compatibility and performance characteristics

Test Coverage Assessment ✅

• Existing Coverage: The codebase has comprehensive F# test projects that will validate the update
• No Additional Tests Needed: For a patch version dependency update, existing tests provide adequate coverage
• Automated Testing: The CI pipeline will validate all F# functionality works with the new version

Recommendations

1. ✅ Approve: This is a safe patch update from a trusted source
2. ✅ Auto-merge: Perfect candidate for Renovate's auto-merge feature
3. ✅ Monitor: CI tests will catch any unexpected issues

---

[claude]

Claude finished @thomhurst's task —— View job

---

PR Review: FSharp.Core Dependency Update

Todo List:

• Read repository guidelines (CLAUDE.md) - No CLAUDE.md found
• Analyze the changed file (Directory.Packages.props)
• Check for F# projects that would be affected
• Research FSharp.Core 9.0.303 changes and potential breaking changes
• Assess security implications
• Evaluate performance considerations
• Review test coverage needs
• Provide comprehensive review feedback

---

Review Summary ✅

This is a low-risk patch update that looks good to merge. Here's my detailed analysis:

Code Quality & Best Practices ✅

• Centralized Package Management: Properly using Directory.Packages.props for version management at line 16
• Single Responsibility: Clean, focused change updating only FSharp.Core version
• Semantic Versioning: Following proper patch version increment (9.0.300 → 9.0.303)

Potential Issues & Breaking Changes ✅

• Patch Version: This is a patch release, so no breaking changes expected
• F# Projects Impact: Found 9 F# projects in the codebase that will benefit from this update:
  • TUnit.TestProject.FSharp/ - Main F# test project
  • TUnit.Assertions.FSharp/ - F# assertions library
  • TUnit.Templates/content/TUnit.FSharp/ - F# project templates
  • Various template snapshot and testing projects
• Dependencies: All F# projects reference FSharp.Core via centralized package management, ensuring consistency

Security Considerations ✅

• Official Package: FSharp.Core is Microsoft's official F# runtime library
• Trusted Source: Updates come from Microsoft's official NuGet feed
• No Security Concerns: Patch versions typically contain bug fixes and performance improvements

Performance Considerations ✅

• Runtime Improvements: Patch updates often include performance optimizations
• No Degradation Expected: Patch versions maintain API compatibility and performance characteristics

Test Coverage Assessment ✅

• Existing Coverage: The codebase has comprehensive F# test projects that will validate the update
• No Additional Tests Needed: For a patch version dependency update, existing tests provide adequate coverage
• Automated Testing: The CI pipeline will validate all F# functionality works with the new version

Recommendations

1. ✅ Approve: This is a safe patch update from a trusted source
2. ✅ Auto-merge: Perfect candidate for Renovate's auto-merge feature
3. ✅ Monitor: CI tests will catch any unexpected issues

---