Skip to content

⬆️ chore: upgrade dependency ConfirmSteps.Net to 0.2.1 - #52

Open
renovate[bot] wants to merge 1 commit into
developfrom
renovate/confirmsteps.net-0.x
Open

⬆️ chore: upgrade dependency ConfirmSteps.Net to 0.2.1#52
renovate[bot] wants to merge 1 commit into
developfrom
renovate/confirmsteps.net-0.x

Conversation

@renovate

@renovate renovate Bot commented Jun 14, 2026

Copy link
Copy Markdown

This PR contains the following updates:

Package Change Age Confidence
ConfirmSteps.Net 0.1.20.2.1 age confidence

Release Notes

gcelet/ConfirmSteps.Net (ConfirmSteps.Net)

v0.2.0

Official Release Artifacts

Changelog

  • e14de2f ⬆️ chore: upgrade dependencies
  • 05986e9 ✨ feat: add reporting of execution summary of a scenario
  • 10a9e41 ✨ feat: expose http response headers
  • 6eb8a57 ♻️ refactor: allow multiple http verifications
  • f7fafd8 ✨ feat: add step title
  • d7a52de ⬆️ chore: upgrade dependencies
  • f51f65f 🚨 fix: remove warnings introduced by analyzers
  • 1a4c10e 📝 doc: document public api
  • 78d014c ✨ feat: add support for dotnet 8 and 10

Full Changelog: gcelet/ConfirmSteps.Net@v0.1.2...v0.2.0

Breaking changes

  • Headers property type on ConfirmSteps.Steps.Http.Rest.HttpResponseJson change from System.Net.Http.Headers.HttpResponseHeaders to System.Net.Http.Headers.HttpHeaders

Thanks!

Those were the changes on v0.2.0!


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants