[dependabot]

Updated WireMock.Net from 2.15.0 to 2.16.0.

Release notes

Sourced from WireMock.Net's releases.

2.16.0

What's Changed

• Fix #​1501: Generate WhenStateIs/WillSetStateTo correctly in ToCSharpCode by @​Bafyn in Fix #1501: Generate WhenStateIs/WillSetStateTo correctly in ToCSharpCode wiremock/WireMock.Net#1502
• Fix FormUrlEncodedMatcher (+ refactor values / matchers logic) by @​StefH in Fix FormUrlEncodedMatcher (+ refactor values / matchers logic) wiremock/WireMock.Net#1503
• Update SharpYaml package to version 2.5.1 by @​johnthcall in Update SharpYaml package to version 2.5.1 wiremock/WireMock.Net#1504
• Upgrade dependency RamlToOpenApiConverter to version 0.40.0 by @​StefH in Upgrade dependency RamlToOpenApiConverter to version 0.40.0 wiremock/WireMock.Net#1505

Full Changelog: wiremock/WireMock.Net@2.15.0...2.16.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: packages. Please create it before Dependabot can add it 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

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: b816807b-ce2a-4675-966d-55bb2fed6e2a

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[guibranco]

Automatically approved by gstraccini[bot]

[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.}

[github-actions]

Infisical secrets check: ✅ No secrets leaked!

💻 Scan logs

2026-09-21T17:37:16Z INF scanning for exposed secrets...
5:37PM INF 598 commits scanned.
2026-09-21T17:37:16Z INF scan completed in 89.5ms
2026-09-21T17:37:16Z INF no leaks found

[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.15.0 ⏵ 2.16.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 microsoft.openapi.yamlreader Location: Package overview From: Tests/SolutionName.IntegrationTests/SolutionName.IntegrationTests.csproj → nuget/wiremock.net@2.16.0 → nuget/microsoft.openapi.yamlreader@3.10.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/microsoft.openapi.yamlreader@3.10.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		Network access: nuget microsoft.openapi Location: Package overview From: Tests/SolutionName.IntegrationTests/SolutionName.IntegrationTests.csproj → nuget/wiremock.net@2.16.0 → nuget/microsoft.openapi@3.10.2 ℹ 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/microsoft.openapi@3.10.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		Dynamic code execution: nuget microsoft.openapi Location: Package overview From: Tests/SolutionName.IntegrationTests/SolutionName.IntegrationTests.csproj → nuget/wiremock.net@2.16.0 → nuget/microsoft.openapi@3.10.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/microsoft.openapi@3.10.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		Network access: nuget ramltoopenapiconverter Location: Package overview From: Tests/SolutionName.IntegrationTests/SolutionName.IntegrationTests.csproj → nuget/wiremock.net@2.16.0 → nuget/ramltoopenapiconverter@0.40.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/ramltoopenapiconverter@0.40.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 ramltoopenapiconverter Location: Package overview From: Tests/SolutionName.IntegrationTests/SolutionName.IntegrationTests.csproj → nuget/wiremock.net@2.16.0 → nuget/ramltoopenapiconverter@0.40.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/ramltoopenapiconverter@0.40.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 microsoft.openapi.yamlreader Location: Package overview From: Tests/SolutionName.IntegrationTests/SolutionName.IntegrationTests.csproj → nuget/wiremock.net@2.16.0 → nuget/microsoft.openapi.yamlreader@3.10.2 ℹ 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/microsoft.openapi.yamlreader@3.10.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		Filesystem access: nuget microsoft.openapi Location: Package overview From: Tests/SolutionName.IntegrationTests/SolutionName.IntegrationTests.csproj → nuget/wiremock.net@2.16.0 → nuget/microsoft.openapi@3.10.2 ℹ 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/microsoft.openapi@3.10.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		Filesystem access: nuget ramltoopenapiconverter Location: Package overview From: Tests/SolutionName.IntegrationTests/SolutionName.IntegrationTests.csproj → nuget/wiremock.net@2.16.0 → nuget/ramltoopenapiconverter@0.40.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/ramltoopenapiconverter@0.40.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

[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]

A newer version of WireMock.Net exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged.

[guibranco]

@dependabot recreate

[pr-code-reviewer]

👋 Hi there!

Everything looks good!

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

[dependabot]

Looks like WireMock.Net is updatable in another way, so this is no longer needed.

[dependabot]

Oh no! Something went wrong on our end. Please try again later.

If the problem persists, please contact GitHub support for assistance 🙇