Bump WireMock.Net from 2.6.0 to 2.9.0

[dependabot]

Updated WireMock.Net from 2.6.0 to 2.9.0.

Release notes

Sourced from WireMock.Net's releases.

2.9.0

What's Changed

• Fix WireMock.Net.Aspire project when using Aspire 13.4.0 by @​StefH in Fix WireMock.Net.Aspire project when using Aspire 13.4.0 wiremock/WireMock.Net#1470

Full Changelog: wiremock/WireMock.Net@2.8.0...2.9.0

2.8.0

What's Changed

• Add SystemTextJsonMatchers by @​StefH in Add SystemTextJsonMatchers wiremock/WireMock.Net#1447
• Bump System.Net.Http from 4.3.0 to 4.3.4 in Aspire Example project by @​dependabot[bot] in Bump System.Net.Http from 4.3.0 to 4.3.4 in Aspire Example project wiremock/WireMock.Net#1467
• Bump System.Text.RegularExpressions from 4.3.0 to 4.3.1 in Aspire Example project by @​dependabot[bot] in Bump System.Text.RegularExpressions from 4.3.0 to 4.3.1 in Aspire Example project wiremock/WireMock.Net#1466
• Update JsonMatcher to support IgnoreArrayOrder by @​StefH in Update JsonMatcher to support IgnoreArrayOrder wiremock/WireMock.Net#1468

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

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.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Labels

The following labels could not be found: nuget, packages. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[semanticdiff-com]

Review changes with  

Changed Files

File	Status
Tests/SolutionName.IntegrationTests/SolutionName.IntegrationTests.csproj	0% smaller

[pr-code-reviewer]

👋 Hi there!

Update the WireMock.Net package reference from version 2.6.0 to 2.9.0 for integration testing consistency and possibly bug fixes or new features. Check for compatibility issues or breaking changes that might affect other parts of the codebase due to this package update. Ensure that all tests pass after making this change to confirm the compatibility and functionality of the updated package version.

_{^{Automatically generated with the help of gpt-3.5-turbo.
Feedback? Please don't hesitate to drop me an email at webber@takken.io.}}

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

_{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.}

[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.9.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		Dynamic code execution: nuget json.more.net Location: Package overview From: Tests/SolutionName.IntegrationTests/SolutionName.IntegrationTests.csproj → nuget/wiremock.net@2.9.0 → nuget/json.more.net@3.0.1 ℹ 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/json.more.net@3.0.1. 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 jsonconverter.system.text.json Location: Package overview From: Tests/SolutionName.IntegrationTests/SolutionName.IntegrationTests.csproj → nuget/wiremock.net@2.9.0 → nuget/jsonconverter.system.text.json@0.12.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/jsonconverter.system.text.json@0.12.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 jsonpath.net Location: Package overview From: Tests/SolutionName.IntegrationTests/SolutionName.IntegrationTests.csproj → nuget/wiremock.net@2.9.0 → nuget/jsonpath.net@3.0.2 ℹ 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/jsonpath.net@3.0.2. 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		Low adoption: nuget wiremock.net.matchers.systemtextjsonpath Location: Package overview From: Tests/SolutionName.IntegrationTests/SolutionName.IntegrationTests.csproj → nuget/wiremock.net@2.9.0 → nuget/wiremock.net.matchers.systemtextjsonpath@2.9.0 ℹ Read more on: This package | This alert | What are unpopular packages? 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: Unpopular packages may have less maintenance and contain other problems. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore nuget/wiremock.net.matchers.systemtextjsonpath@2.9.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 wiremock.net.matchers.systemtextjsonpath Location: Package overview From: Tests/SolutionName.IntegrationTests/SolutionName.IntegrationTests.csproj → nuget/wiremock.net@2.9.0 → nuget/wiremock.net.matchers.systemtextjsonpath@2.9.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/wiremock.net.matchers.systemtextjsonpath@2.9.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 jsonconverter.system.text.json Location: Package overview From: Tests/SolutionName.IntegrationTests/SolutionName.IntegrationTests.csproj → nuget/wiremock.net@2.9.0 → nuget/jsonconverter.system.text.json@0.12.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/jsonconverter.system.text.json@0.12.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

[guibranco]

Automatically approved by gstraccini[bot]

[github-actions]

Infisical secrets check: ✅ No secrets leaked!

💻 Scan logs

2026-06-03T13:23:23Z INF scanning for exposed secrets...
1:23PM INF 529 commits scanned.
2026-06-03T13:23:23Z INF scan completed in 79.8ms
2026-06-03T13:23:23Z INF no leaks found

[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