Bump WireMock.Net from 1.5.58 to 1.5.59

[dependabot[bot]]

Bumps WireMock.Net from 1.5.58 to 1.5.59.

Changelog

Sourced from WireMock.Net's changelog.

1.5.59 (26 June 2024)

• #1127 - Made changes to accommodate breaking change in testcontainers-dotnet 3.9 [feature] contributed by epDugas

Commits

• 4d83d82 1.5.59
• bf28ba7 Made changes to accommodate breaking change in testcontainers-dotnet v3.9. (#...
• 90e017b Use dotnet sonar scanner (part 2) (#1125)
• 2602db5 Revert Sonar to old way (#1124)
• 61937db Fix SonarCloud integration (#1123)
• 8a60950 Fix link to ci.yml
• See full diff 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 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)

[guibranco]

@dependabot squash and merge

[dependabot[bot]]

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.

[AppVeyorBot]

:x: Build CEPAberto 4.0.390 failed (commit https://github.com/guibranco/CEPAberto/commit/26896fd548 by @dependabot[bot])

[guibranco]

@gstraccini appveyor build commit

[guibranco]

@gstraccini appveyor build pull request

[gstraccini[bot]]

AppVeyor build (commit) started! :rocket:

Build ID: 50162799 Version: 4.0.391

[gstraccini[bot]]

AppVeyor build (pull request) started! :rocket:

Build ID: 50162800 Version: 4.0.392

[AppVeyorBot]

:x: Build CEPAberto 4.0.392 failed (commit https://github.com/guibranco/CEPAberto/commit/26896fd548 by @dependabot[bot])

[AppVeyorBot]

:x: Build CEPAberto 4.0.397 failed (commit https://github.com/guibranco/CEPAberto/commit/a040c416e1 by @guibranco)

[guibranco]

@gstraccini review

[gstraccini[bot]]

Reviewing this pull request.

Commits included: SHA: ebeaeb5df746b943744aa1c9654310e20e94c818 SHA: 70066264ca3c8fbc7586c2002fe4d5c3a523bcd7 ! :eyes:

[dependabot[bot]]

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

[gitguardian[bot]]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

| GitGuardian id | GitGuardian status | Secret | Commit | Filename | | | -------------- | ------------------ | ------------------------------ | ---------------- | --------------- | -------------------- | | [5444983](https://dashboard.gitguardian.com/workspace/7014/incidents/5444983?occurrence=160733352) | Triggered | Generic High Entropy Secret | 80a0e5419dd12b0e0dbd5b292a277b43907d1378 | Tests/CEPAberto.Tests/CEPAbertoClientTest.cs | [View secret](https://github.com/guibranco/CEPAberto/commit/80a0e5419dd12b0e0dbd5b292a277b43907d1378#diff-9c8fef13f09ea1f1098a957eba172dbb2cab9a3482a4a965bade065bedbdee23L5) |

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code. 2. Replace and store your secret safely. [Learn here](https://blog.gitguardian.com/secrets-api-management?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) the best practices. 3. Revoke and [rotate this secret](https://docs.gitguardian.com/secrets-detection/secrets-detection-engine/detectors/generics/generic_high_entropy_secret#revoke-the-secret?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). 4. If possible, [rewrite git history](https://blog.gitguardian.com/rewriting-git-history-cheatsheet?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data. To avoid such incidents in the future consider - following these [best practices](https://blog.gitguardian.com/secrets-api-management/?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) for managing and storing secrets including API keys and other credentials - install [secret detection on pre-commit](https://docs.gitguardian.com/ggshield-docs/integrations/git-hooks/pre-commit?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[dependabot[bot]]

Superseded by #181.

[AppVeyorBot]

:x: Build CEPAberto 4.0.414 failed (commit https://github.com/guibranco/CEPAberto/commit/6f23dd95c8 by @guibranco)