Skip to content

chore(deps): bump WireMock.Net to 2.13.0 across test projects - #94

Merged
blehnen merged 1 commit into
mainfrom
chore/wiremock-2.13
Jul 23, 2026
Merged

chore(deps): bump WireMock.Net to 2.13.0 across test projects#94
blehnen merged 1 commit into
mainfrom
chore/wiremock-2.13

Conversation

@blehnen

@blehnen blehnen commented Jul 23, 2026

Copy link
Copy Markdown
Owner

Summary

Completes the WireMock alignment. #92's squash landed the 9 test projects at 2.11.0 (its commit message said 2.13.0) while the Scriban pin was already raised to 7.2.5. This bumps all 9 test projects to 2.13.0 for real, matching the pin, and supersedes the recurring Dependabot 2.13 bump.

The tests/Directory.Build.props pin (Scriban.Signed 7.2.5) already covers 2.13's floor — no NU1902 (patched) and no NU1605 (7.2.5 ≥ floor).

Type of change

  • Build / CI / docs
  • Refactor / chore

Checklist

  • Build green: dotnet build FrigateRelay.sln -c Release (0/0, forced restore)
  • Tests pass: bash .github/scripts/run-tests.sh (314 unit tests; integration skipped — needs Docker)

Notes for reviewer

9 .csproj, 2.11.0 → 2.13.0 only. Verified with dotnet restore --force + dotnet nuget why that Scriban resolves to the pinned 7.2.5 (not the transitive 7.2.0) — the lesson from the prior iteration where a warm cache masked the real resolution.

Completes the WireMock alignment: #92's squash landed the test projects at
2.11.0 (the commit message said 2.13.0) while the Scriban pin was already
raised to 7.2.5. This bumps all 9 test projects to 2.13.0 for real, matching
the pin. Supersedes the recurring Dependabot 2.13 bump.

The tests/Directory.Build.props pin (Scriban.Signed 7.2.5) already covers
2.13's floor. Verified with a forced restore: Scriban resolves to 7.2.5 (no
NU1902/NU1605), build 0/0, 314 unit tests pass.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jul 23, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@blehnen, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 43 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: bd22a449-eba8-4f0f-8452-1d9e969800f2

📥 Commits

Reviewing files that changed from the base of the PR and between 10b887a and dba8b9e.

📒 Files selected for processing (9)
  • tests/FrigateRelay.Host.Tests/FrigateRelay.Host.Tests.csproj
  • tests/FrigateRelay.IntegrationTests.RealBroker/FrigateRelay.IntegrationTests.RealBroker.csproj
  • tests/FrigateRelay.IntegrationTests/FrigateRelay.IntegrationTests.csproj
  • tests/FrigateRelay.Plugins.BlueIris.Tests/FrigateRelay.Plugins.BlueIris.Tests.csproj
  • tests/FrigateRelay.Plugins.CodeProjectAi.Tests/FrigateRelay.Plugins.CodeProjectAi.Tests.csproj
  • tests/FrigateRelay.Plugins.Doods2.Tests/FrigateRelay.Plugins.Doods2.Tests.csproj
  • tests/FrigateRelay.Plugins.FrigateSnapshot.Tests/FrigateRelay.Plugins.FrigateSnapshot.Tests.csproj
  • tests/FrigateRelay.Plugins.Pushover.Tests/FrigateRelay.Plugins.Pushover.Tests.csproj
  • tests/FrigateRelay.Plugins.Roboflow.Tests/FrigateRelay.Plugins.Roboflow.Tests.csproj

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@sonarqubecloud

Copy link
Copy Markdown

@codecov

codecov Bot commented Jul 23, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 91.50%. Comparing base (10b887a) to head (dba8b9e).

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #94   +/-   ##
=======================================
  Coverage   91.50%   91.50%           
=======================================
  Files          61       61           
  Lines        1860     1860           
  Branches      289      289           
=======================================
  Hits         1702     1702           
  Misses         82       82           
  Partials       76       76           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@blehnen
blehnen merged commit fe4a375 into main Jul 23, 2026
16 checks passed
@blehnen
blehnen deleted the chore/wiremock-2.13 branch July 23, 2026 22:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant