Bump WireMock.Net from 1.9.0 to 1.9.1

[dependabot]

Updated WireMock.Net from 1.9.0 to 1.9.1.

Release notes

Sourced from WireMock.Net's releases.

1.9.1

What's Changed

• Add TimesInSameState to MappingModel by @​StefH in Add TimesInSameState to MappingModel wiremock/WireMock.Net#1345
• Fix generating source code for Scenario and State by @​StefH in Fix generating source code for Scenario and State wiremock/WireMock.Net#1347

Full Changelog: wiremock/WireMock.Net@1.9.0...1.9.1

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 the WireMock.Net package version from 1.9.0 to 1.9.1 in the SolutionName.IntegrationTests project file.

Why are these changes being made?

This update is made to apply the latest bug fixes and improvements available in WireMock.Net 1.9.1. Keeping dependencies up to date helps maintain software stability and security.

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

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

[instapr]

Feedback:

• Updated WireMock.Net from 1.9.0 to 1.9.1.
• Changes include:
  • Added TimesInSameState to MappingModel.
  • Fixed generating source code for Scenario and State.
• Full Changelog: WireMock.Net 1.9.0 to 1.9.1

No further action required.

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

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Join our Discord community for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[codara-ai-code-review]

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

1. /Tests/SolutionName.IntegrationTests/SolutionName.IntegrationTests.csproj - The upgrade from WireMock.Net version 1.9.0 to 1.9.1 may introduce breaking changes or deprecations that could potentially affect existing test functionality. It is crucial to verify the release notes for version 1.9.1 to ensure that the changes do not break any of your existing tests.

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

1. /Tests/SolutionName.IntegrationTests/SolutionName.IntegrationTests.csproj - Whenever you upgrade a dependency in your project, consider running all tests associated with that dependency immediately after the change. This practice helps catch any issues introduced by the new version early in the development cycle.
2. /Tests/SolutionName.IntegrationTests/SolutionName.IntegrationTests.csproj - It is advisable to pin version numbers with a Patch version increment (.x.x), ensuring you do not unintentionally include future-breaking changes, especially in a CI/CD pipeline. You might consider using a versioning strategy that allows only patches or minor updates unless explicitly tested.
3. /Tests/SolutionName.IntegrationTests/SolutionName.IntegrationTests.csproj - Document your package version changes (including rationale) in a changelog or within your version control system to maintain clarity about changes made during dependency updates. This aids in troubleshooting potential issues that arise later on.

[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.0 ⏵ 1.9.1

View full report

[github-actions]

Infisical secrets check: ✅ No secrets leaked!

💻 Scan logs

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

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

12:33AM INF scanning for exposed secrets...
12:33AM INF 438 commits scanned.
12:33AM INF scan completed in 70.7ms
12:33AM 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