Skip to content

Bump WireMock.Net from 2.3.0 to 2.5.0#288

Merged
guibranco merged 3 commits into
mainfrom
dependabot/nuget/Tests/LatLongNet.IntegrationTests/WireMock.Net-2.5.0
May 13, 2026
Merged

Bump WireMock.Net from 2.3.0 to 2.5.0#288
guibranco merged 3 commits into
mainfrom
dependabot/nuget/Tests/LatLongNet.IntegrationTests/WireMock.Net-2.5.0

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github May 4, 2026

Updated WireMock.Net from 2.3.0 to 2.5.0.

Release notes

Sourced from WireMock.Net's releases.

2.5.0

What's Changed

New Contributors

Full Changelog: wiremock/WireMock.Net@2.4.0...2.5.0

2.4.0

What's Changed

Full Changelog: wiremock/WireMock.Net@2.3.0...2.4.0

Commits viewable in compare view.

Dependabot compatibility score

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)

---
updated-dependencies:
- dependency-name: WireMock.Net
  dependency-version: 2.5.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added .NET Pull requests that update .net code dependencies Dependencies nuget packages labels May 4, 2026
@github-actions github-actions Bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label May 4, 2026
@socket-security
Copy link
Copy Markdown

socket-security Bot commented May 4, 2026

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updatedwiremock.net@​2.3.0 ⏵ 2.5.09910090100100

View full report

@socket-security
Copy link
Copy Markdown

socket-security Bot commented May 4, 2026

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 Medium
Network access: nuget opentelemetry

Location: Package overview

From: Tests/LatLongNet.IntegrationTests/LatLongNet.IntegrationTests.csprojnuget/wiremock.net@2.5.0nuget/opentelemetry@1.15.3

ℹ 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/opentelemetry@1.15.3. 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

@codacy-production
Copy link
Copy Markdown

codacy-production Bot commented May 4, 2026

Not up to standards ⛔

🟢 Coverage ∅ diff coverage · +0.00% coverage variation

Metric Results
Coverage variation +0.00% coverage variation (-1.00%)
Diff coverage diff coverage

View coverage diff in Codacy

Coverage variation details
Coverable lines Covered lines Coverage
Common ancestor commit (5233c47) 8 8 100.00%
Head commit (36122c5) 8 (+0) 8 (+0) 100.00% (+0.00%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details
Coverable lines Covered lines Diff coverage
Pull request (#288) 0 0 ∅ (not applicable)

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

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.

@AppVeyorBot
Copy link
Copy Markdown

@codecov
Copy link
Copy Markdown

codecov Bot commented May 4, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (5233c47) to head (36122c5).

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #288   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            1         1           
  Lines            8         8           
=========================================
  Hits             8         8           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@guibranco guibranco enabled auto-merge (squash) May 5, 2026 04:59
@gstraccini gstraccini Bot added the ☑️ auto-merge Automatic merging of pull requests (gstraccini-bot) label May 5, 2026
@gstraccini gstraccini Bot added the 🤖 bot Automated processes or integrations label May 5, 2026
@dependabot @github
Copy link
Copy Markdown
Contributor Author

dependabot Bot commented on behalf of github May 12, 2026

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.

Copy link
Copy Markdown
Owner

@guibranco guibranco left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Automatically approved by gstraccini[bot]

@github-actions
Copy link
Copy Markdown

Infisical secrets check: ✅ No secrets leaked!

💻 Scan logs
2026-05-13T10:14:41Z INF scanning for exposed secrets...
10:14AM INF 268 commits scanned.
2026-05-13T10:14:41Z INF scan completed in 51.8ms
2026-05-13T10:14:41Z INF no leaks found

@sonarqubecloud
Copy link
Copy Markdown

@AppVeyorBot
Copy link
Copy Markdown

Build LatLongNet-SDK-dotnet 2.2.754 completed (commit 7b625869af by @gstraccini[bot])

@guibranco guibranco disabled auto-merge May 13, 2026 14:40
@guibranco guibranco merged commit 4184c7c into main May 13, 2026
22 of 24 checks passed
@guibranco guibranco deleted the dependabot/nuget/Tests/LatLongNet.IntegrationTests/WireMock.Net-2.5.0 branch May 13, 2026 14:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

☑️ auto-merge Automatic merging of pull requests (gstraccini-bot) 🤖 bot Automated processes or integrations dependencies Dependencies .NET Pull requests that update .net code nuget packages size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants