fix(csharp): bump WireMock.Net to 2.6.0 in generated test projects#15873
Conversation
There was a problem hiding this comment.
Claude Code Review
This repository is configured for manual code reviews. Comment @claude review to trigger a review and subscribe this PR to future pushes, or @claude review once for a one-time review.
Tip: disable this comment in your organization's Code Review settings.
SDK Generation Benchmark ResultsComparing PR branch against median of 5 nightly run(s) on Full benchmark table (click to expand)
main (generator): generator-only time via --skip-scripts (includes Docker image build, container startup, IR parsing, and code generation — this is the same Docker-based flow customers use via |
Closes FER-10540
Summary
WireMock.Net 2.2.0in their generated C# SDK test project (failing job). The version was hardcoded in our shared test-project template, so every C# SDK ships with the same pinned 2.2.0.2.6.0(latest stable on NuGet). Test-only dependency, no runtime impact on SDK consumers.Example
Before —
generators/csharp/base/src/asIs/test/Template.Test.csproj:After:
All 174
seed/csharp-sdk/**/<Project>.Test.csprojsnapshots were regenerated to reflect the bump — the only content change across them is the version string.Test plan
pnpm seed test --generator csharp-sdk --local --skip-scripts— 174/174 fixtures passgit diff --unified=0 | grep -E "^[+-][^+-]"confirms every changed line is theWireMock.Net Versionbump (350 lines, all matching)🤖 Generated with Claude Code