Bump WireMock.Net from 1.9.1 to 1.12.0

[dependabot]

Updated WireMock.Net from 1.9.1 to 1.12.0.

Release notes

Sourced from WireMock.Net's releases.

1.12.0

What's Changed

• Upgrade Testcontainers to 4.7.0 by @​StefH in Upgrade Testcontainers to 4.7.0 wiremock/WireMock.Net#1357

Full Changelog: wiremock/WireMock.Net@1.11.2...1.12.0

1.11.2

What's Changed

• Add additional try-catch to TypeLoader logic by @​StefH in Add additional try-catch to TypeLoader logic wiremock/WireMock.Net#1352
• Add System.Net.Http again to solve CVE warning by @​StefH in Add System.Net.Http again to solve CVE warning wiremock/WireMock.Net#1354
• Revert JetBrains.Annotations and add System.Text.RegularExpressions t… by @​StefH in Revert JetBrains.Annotations and add System.Text.RegularExpressions t… wiremock/WireMock.Net#1355

Full Changelog: wiremock/WireMock.Net@1.11.0...1.11.2

1.11.0

What's Changed

• Create WireMock.Net.ProtoBuf project by @​StefH in Create WireMock.Net.ProtoBuf project wiremock/WireMock.Net#1350

Full Changelog: wiremock/WireMock.Net@1.10.1...1.11.0

1.10.1

What's Changed

• Add AtPath and AtAbsolutePath to Assertions projects by @​StefH in Add AtPath and AtAbsolutePath to Assertions projects wiremock/WireMock.Net#1349

Full Changelog: wiremock/WireMock.Net@1.10.0...1.10.1

1.10.0

What's Changed

• Add new package WireMock.Net.Extensions.Routing which provides minimal-API-style routing for WireMock.Net by @​GennadyGS in Add new package WireMock.Net.Extensions.Routing which provides minimal-API-style routing for WireMock.Net wiremock/WireMock.Net#1344

New Contributors

• @​GennadyGS made their first contribution in Add new package WireMock.Net.Extensions.Routing which provides minimal-API-style routing for WireMock.Net wiremock/WireMock.Net#1344

Full Changelog: wiremock/WireMock.Net@1.9.1...1.10.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 will merge this PR once CI passes on it, as requested by @guibranco.

---

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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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)

Description by Korbit AI

What change is being made?

Bump WireMock.Net from version 1.9.1 to 1.12.0 in the project file.

Why are these changes being made?

The update to WireMock.Net's latest version ensures compatibility with recent updates, new features, and bug fixes, which improves the integration test reliability and overall code maintainability. This change is necessary to keep the dependencies updated and make use of the improvements and optimizations in the newer version.

Is this description stale? Ask me to generate a new description by commenting /korbit-generate-pr-description

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

Everything looks good!

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

[codara-ai-code-review]

Potential issues, bugs, and flaws that can introduce unwanted behavior.

1. Version Compatibility Risk
   /Tests/SolutionName.IntegrationTests/SolutionName.IntegrationTests.csproj
   Upgrading WireMock.Net from version 1.9.1 to 1.12.0 could introduce breaking changes if the new version has any major modifications or deprecations that affect existing test logic or functionality. Be sure to review the release notes and test thoroughly to ensure compatibility and stability.

Code suggestions and improvements for better exception handling, logic, standardization, and consistency.

1. Dependency Management
   /Tests/SolutionName.IntegrationTests/SolutionName.IntegrationTests.csproj
   As a best practice, consider managing package version updates using a package version management tool or a centralized versioning system (e.g., Directory.Packages.props in SDK-style projects). This can help with consistent versioning across projects in the solution and ease future upgrades.

[korbit-ai]

By default, I don't review pull requests opened by bots. If you would like me to review this pull request anyway, you can request a review via the /korbit-review command in a comment.

[coderabbitai]

Important

Review skipped

Bot user detected.

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

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

---

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

[guibranco]

Automatically approved by gstraccini[bot]

[guibranco]

@dependabot squash and merge

[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.9.1 ⏵ 1.12.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		[email protected] Uses eval. Location: Package overview From: Tests/SolutionName.IntegrationTests/SolutionName.IntegrationTests.csproj → nuget/[email protected] ℹ 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 [email protected]. 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/[email protected]. 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		[email protected] is an Unpopular package. Location: Package overview From: Tests/SolutionName.IntegrationTests/SolutionName.IntegrationTests.csproj → nuget/[email protected] → nuget/[email protected] ℹ 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 [email protected]. 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/[email protected]. 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		[email protected] Uses eval. Location: Package overview From: Tests/SolutionName.IntegrationTests/SolutionName.IntegrationTests.csproj → nuget/[email protected] → nuget/[email protected] ℹ 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 [email protected]. 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/[email protected]. 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		[email protected] has Filesystem access. Location: Package overview From: Tests/SolutionName.IntegrationTests/SolutionName.IntegrationTests.csproj → nuget/[email protected] → nuget/[email protected] ℹ 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 [email protected]. 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/[email protected]. 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

[dependabot]

One of your CI runs failed on this pull request, so Dependabot won't merge it.

Dependabot will still automatically merge this pull request if you amend it and your tests pass.

[github-actions]

Infisical secrets check: ✅ No secrets leaked!

💻 Scan logs

A new release of infisical is available: 0.41.90 -> 0.41.99

To update, run: sudo apt-get update && sudo apt-get install infisical

6:03PM INF scanning for exposed secrets...
6:03PM INF 446 commits scanned.
6:03PM INF scan completed in 75.2ms
6:03PM 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