Bump WireMock.Net from 2.6.0 to 2.7.0

[dependabot]

Updated WireMock.Net from 2.6.0 to 2.7.0.

Release notes

Sourced from WireMock.Net's releases.

2.7.0

What's Changed

• Update OpenTelemetry.Api from 1.14.0 to 1.15.3 in unit test project by @​dependabot[bot] in Update OpenTelemetry.Api from 1.14.0 to 1.15.3 in unit test project wiremock/WireMock.Net#1457
• chore: update Handlebars 2.5.2 to 2.5.5 by @​kamisoft-fr in chore: update Handlebars 2.5.2 to 2.5.5 wiremock/WireMock.Net#1459
• Update Testcontainers nuget package to 4.12.0 by @​MD-V in Update Testcontainers nuget package to 4.12.0 wiremock/WireMock.Net#1461
• Update Scriban.Signed to latest by @​StefH in Update Scriban.Signed to latest wiremock/WireMock.Net#1462
• Trusted Publishing by @​StefH in Trusted Publishing wiremock/WireMock.Net#1465

New Contributors

• @​kamisoft-fr made their first contribution in chore: update Handlebars 2.5.2 to 2.5.5 wiremock/WireMock.Net#1459

Full Changelog: wiremock/WireMock.Net@2.6.0...2.7.0

Commits viewable in compare view.

[guibranco]

Automatically approved by gstraccini[bot]

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	wiremock.net@​2.6.0 ⏵ 2.7.0

View full report

[socket-security]

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Block		Network access: nuget scriban.signed Location: Package overview From: Tests/LatLongNet.IntegrationTests/LatLongNet.IntegrationTests.csproj → nuget/wiremock.net@2.7.0 → nuget/scriban.signed@7.2.0 ℹ Read more on: This package | This alert | What is network access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore nuget/scriban.signed@7.2.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Dynamic code execution: nuget scriban.signed Location: Package overview From: Tests/LatLongNet.IntegrationTests/LatLongNet.IntegrationTests.csproj → nuget/wiremock.net@2.7.0 → nuget/scriban.signed@7.2.0 ℹ Read more on: This package | This alert | What is dynamic code execution? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Avoid packages that use dynamic code execution like eval(), since this could potentially execute any code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore nuget/scriban.signed@7.2.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Filesystem access: nuget scriban.signed Location: Package overview From: Tests/LatLongNet.IntegrationTests/LatLongNet.IntegrationTests.csproj → nuget/wiremock.net@2.7.0 → nuget/scriban.signed@7.2.0 ℹ Read more on: This package | This alert | What is filesystem access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore nuget/scriban.signed@7.2.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[codacy-production]

Not up to standards ⛔

🟢 Coverage ∅ diff coverage · +0.00% coverage variation

Metric	Results
Coverage variation	✅ +0.00% coverage variation (-1.00%)
Diff coverage	✅ ∅ diff coverage

View coverage diff in Codacy

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (a71efc2)	8	8	100.00%
Head commit (91f5687)	8 (+0)	8 (+0)	100.00% (+0.00%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#296)	0	0	∅ (not applicable)

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[AppVeyorBot]

✅ Build LatLongNet-SDK-dotnet 2.2.781 completed (commit c3d7dfac36 by @dependabot[bot])

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (a71efc2) to head (91f5687).

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #296   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            1         1           
  Lines            8         8           
=========================================
  Hits             8         8           

☔ View full report in Codecov by Sentry.
📢 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.

[guibranco]

@dependabot recreate

[github-actions]

Infisical secrets check: ✅ No secrets leaked!

💻 Scan logs

2026-05-26T15:05:17Z INF scanning for exposed secrets...
3:05PM INF 275 commits scanned.
2026-05-26T15:05:17Z INF scan completed in 35.9ms
2026-05-26T15:05:17Z INF no leaks found

[AppVeyorBot]

❌ Build LatLongNet-SDK-dotnet 2.2.787 failed (commit 6fb8162981 by @dependabot[bot])

[AppVeyorBot]

✅ Build LatLongNet-SDK-dotnet 2.2.788 completed (commit 6fb8162981 by @dependabot[bot])

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[dependabot]

Superseded by #299.