Bump WireMock.Net from 1.25.0 to 2.0.0

[dependabot]

Updated WireMock.Net from 1.25.0 to 2.0.0.

Release notes

Sourced from WireMock.Net's releases.

2.0.0

What's Changed

• MappingSerializer (Newtonsoft or SystemText)-Json by @​StefH in MappingSerializer (Newtonsoft or SystemText)-Json wiremock/WireMock.Net#1394
• Version 2.x by @​StefH in Version 2.x wiremock/WireMock.Net#1359

Full Changelog: wiremock/WireMock.Net@1.25.0...2.0.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!

1. Check compatibility: Ensure that the updated version of "WireMock.Net" (2.0.0) is compatible with other dependencies.
2. Test impact: Verify that upgrading "WireMock.Net" does not introduce breaking changes or affect existing functionality negatively.
3. Update documentation: Update any relevant documentation to reflect the change in the package version for "WireMock.Net."

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

[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@​1.25.0 ⏵ 2.0.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 anyof Location: Package overview From: Tests/SolutionName.IntegrationTests/SolutionName.IntegrationTests.csproj → nuget/wiremock.net@2.0.0 → nuget/anyof@0.5.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/anyof@0.5.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 graphql.newtonsoftjson Location: Package overview From: Tests/SolutionName.IntegrationTests/SolutionName.IntegrationTests.csproj → nuget/wiremock.net@2.0.0 → nuget/graphql.newtonsoftjson@8.5.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/graphql.newtonsoftjson@8.5.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 njsonschema.extensions Location: Package overview From: Tests/SolutionName.IntegrationTests/SolutionName.IntegrationTests.csproj → nuget/wiremock.net@2.0.0 → nuget/njsonschema.extensions@0.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/njsonschema.extensions@0.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 randomdatagenerator.net Location: Package overview From: Tests/SolutionName.IntegrationTests/SolutionName.IntegrationTests.csproj → nuget/wiremock.net@2.0.0 → nuget/randomdatagenerator.net@1.0.19.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/randomdatagenerator.net@1.0.19.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		System shell access: nuget randomdatagenerator.net Location: Package overview From: Tests/SolutionName.IntegrationTests/SolutionName.IntegrationTests.csproj → nuget/wiremock.net@2.0.0 → nuget/randomdatagenerator.net@1.0.19.1 ℹ Read more on: This package | This alert | What is shell 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 avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore nuget/randomdatagenerator.net@1.0.19.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		Filesystem access: nuget graphql.newtonsoftjson Location: Package overview From: Tests/SolutionName.IntegrationTests/SolutionName.IntegrationTests.csproj → nuget/wiremock.net@2.0.0 → nuget/graphql.newtonsoftjson@8.5.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/graphql.newtonsoftjson@8.5.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 randomdatagenerator.net Location: Package overview From: Tests/SolutionName.IntegrationTests/SolutionName.IntegrationTests.csproj → nuget/wiremock.net@2.0.0 → nuget/randomdatagenerator.net@1.0.19.1 ℹ 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/randomdatagenerator.net@1.0.19.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		License exception: nuget system.text.encodings.web with Classpath-exception-2.0 Exception: Classpath-exception-2.0 Comments: From: Tests/SolutionName.IntegrationTests/SolutionName.IntegrationTests.csproj → nuget/wiremock.net@2.0.0 → nuget/system.text.encodings.web@8.0.0 ℹ Read more on: This package | This alert | What is a license exception? 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: License exceptions should be carefully reviewed. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore nuget/system.text.encodings.web@8.0.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-03-20T16:41:54Z INF scanning for exposed secrets...
4:41PM INF 501 commits scanned.
2026-03-20T16:41:54Z INF scan completed in 78.9ms
2026-03-20T16:41:54Z 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