chore(deps): update dependency streamjsonrpc to 2.22.23

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
StreamJsonRpc (source)	nuget	patch	2.22.11 -> 2.22.23

---

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

Todo List:

• Read the changed file to understand the update
• Search codebase for StreamJsonRpc usage
• Assess potential impact and risks
• Provide comprehensive review feedback

Review Summary

This PR updates StreamJsonRpc from version 2.22.11 to 2.22.23 - a minor patch version update.

Code Quality & Best Practices ✅

• Clean dependency management: Uses centralized package versioning via Directory.Packages.props
• Appropriate scope: StreamJsonRpc is only used in test projects (TUnit.RpcTests), limiting blast radius
• Modern usage: Code uses current StreamJsonRpc APIs properly with JsonRpc, HeaderDelimitedMessageHandler, and SystemTextJsonFormatter

Potential Issues & Risks 🟡

• Limited test coverage: The RPC tests are currently skipped ([Test, Skip("TODO: Fix RPC tests")] in Tests.cs:14)
• Untested change: Without active RPC tests running, this version bump cannot be validated automatically
• Critical functionality: The RPC client handles test discovery and execution communication, which is core to TUnit's operation

Performance Considerations ✅

• Patch version: Being a patch release (2.22.11 → 2.22.23), this should only contain bug fixes with no performance regressions
• Minimal scope: Only affects RPC test infrastructure, not core testing framework performance

Security Concerns ✅

• Trusted source: StreamJsonRpc is a Microsoft-maintained library with good security practices
• Patch release: Patch versions typically include security fixes rather than introducing vulnerabilities
• Network isolation: RPC usage is limited to localhost TCP connections for test orchestration

Test Coverage Recommendations ⚠️

1. Re-enable RPC tests: Consider fixing and re-enabling the skipped RPC tests to validate this upgrade
2. Integration testing: Verify that test discovery and execution still work correctly via RPC
3. Compatibility check: Ensure the new version maintains API compatibility with existing usage patterns

Recommendation: APPROVE WITH CAUTIONS

This is a low-risk dependency update, but the lack of active test coverage for the affected functionality is concerning. Consider:

• Unskipping the RPC tests to validate the upgrade
• Running manual integration tests if automated ones aren't feasible
• Monitoring for any RPC-related issues after deployment

[claude]

Claude finished @thomhurst's task —— View job

---

PR Review: StreamJsonRpc Dependency Update

Todo List:

• Read the changed file to understand the update
• Search codebase for StreamJsonRpc usage
• Assess potential impact and risks
• Provide comprehensive review feedback

Review Summary

This PR updates StreamJsonRpc from version 2.22.11 to 2.22.23 - a minor patch version update.

Code Quality & Best Practices ✅

• Clean dependency management: Uses centralized package versioning via Directory.Packages.props:76
• Appropriate scope: StreamJsonRpc is only used in test projects (TUnit.RpcTests), limiting blast radius
• Modern usage: Code uses current StreamJsonRpc APIs properly with JsonRpc, HeaderDelimitedMessageHandler, and SystemTextJsonFormatter

Potential Issues & Risks 🟡

• Limited test coverage: The RPC tests are currently skipped ([Test, Skip("TODO: Fix RPC tests")] in Tests.cs:14)
• Untested change: Without active RPC tests running, this version bump cannot be validated automatically
• Critical functionality: The RPC client handles test discovery and execution communication, which is core to TUnit's operation

Performance Considerations ✅

• Patch version: Being a patch release (2.22.11 → 2.22.23), this should only contain bug fixes with no performance regressions
• Minimal scope: Only affects RPC test infrastructure, not core testing framework performance

Security Concerns ✅

• Trusted source: StreamJsonRpc is a Microsoft-maintained library with good security practices
• Patch release: Patch versions typically include security fixes rather than introducing vulnerabilities
• Network isolation: RPC usage is limited to localhost TCP connections for test orchestration

Test Coverage Recommendations ⚠️

1. Re-enable RPC tests: Consider fixing and re-enabling the skipped RPC tests to validate this upgrade
2. Integration testing: Verify that test discovery and execution still work correctly via RPC
3. Compatibility check: Ensure the new version maintains API compatibility with existing usage patterns

Recommendation: APPROVE WITH CAUTIONS

This is a low-risk dependency update, but the lack of active test coverage for the affected functionality is concerning. Consider:

• Unskipping the RPC tests to validate the upgrade
• Running manual integration tests if automated ones aren't feasible
• Monitoring for any RPC-related issues after deployment