Skip to content
This repository has been archived by the owner on Jan 21, 2025. It is now read-only.

Update dependency RestSharp to v112 #97

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 29, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
RestSharp (source) 106.15.0 -> 112.1.0 age adoption passing confidence

Release Notes

restsharp/RestSharp (RestSharp)

v112.1.0

Compare Source

  • Removed \t from invalid header value characters as the aim was to handle CRLF

Full Changelog: restsharp/RestSharp@112.0.0...112.1.0

v112.0.0

Compare Source

What's Changed

New Contributors

Full Changelog: restsharp/RestSharp@111.4.1...112.0.0

v111.4.1

Compare Source

What's Changed
New Contributors

Full Changelog: restsharp/RestSharp@111.4.0...111.4.1

v111.4.0

Compare Source

What's Changed
New Contributors

Full Changelog: restsharp/RestSharp@111.3.0...111.4.0

v111.3.0

Compare Source

What's Changed
New Contributors

Full Changelog: restsharp/RestSharp@111.2.0...111.3.0

v111.2.0

Compare Source

What's Changed

Full Changelog: restsharp/RestSharp@111.1.0...111.2.0

v111.1.0

Compare Source

v111.0.0

Compare Source

What's Changed
New Contributors

Full Changelog: restsharp/RestSharp@110.2.0...111.0.0

v110.2.0

Compare Source

What's Changed

Full Changelog: restsharp/RestSharp@110.1.0...110.2.0

v110.1.0

Compare Source

What's Changed

Full Changelog: restsharp/RestSharp@110.0.0...110.1.0

v110.0.0

Compare Source

What's Changed
Breaking change

The IRestClient interface signature is different, so any non-standard implementations need to adopt the changes.

To keep DefaultParameters thread-safe, it got a new type DefaultParameters, and request property Parameters has a dedicated type RequestParameter. Code-wise the change is non-breaking as the signatures are the same, but v110 is not binary compatible with previous versions. The difference is that DefaultParameters collection wraps all its mutations in a lock.

Full Changelog: restsharp/RestSharp@109.0.1...110.0.0

v109.0.1

Compare Source

What's Changed

New Contributors

Full Changelog: restsharp/RestSharp@109.0.0...109.0.1

v109.0.0

What's Changed
New Contributors

Full Changelog: restsharp/RestSharp@108.0.3...109.0.0

v108.0.3

Compare Source

What's Changed

New Contributors

Full Changelog: restsharp/RestSharp@108.0.2...108.0.3

v108.0.2

Compare Source

What's Changed

New Contributors

Full Changelog: restsharp/RestSharp@108.0.1...108.0.2

v108.0.1

Compare Source

Full Changelog: restsharp/RestSharp@108.0.0...108.0.1

v108.0.0

Compare Source

What's Changed

New Contributors

Full Changelog: restsharp/RestSharp@107.3.0...108.0.0

v107.3.0

Compare Source

What's Changed
New Contributors

Full Changelog: restsharp/RestSharp@107.2.1...107.3.0

v107.2.1

Compare Source

  • Fixed AddCookie failing with null value as cookie domain

v107.2.0

Compare Source

What's Changed
New Contributors

Full Changelog: restsharp/RestSharp@107.1.2...107.2.0

v107.1.2

Compare Source

v107.1.1

Compare Source

What's Changed
  • Added DataType.Binary and corresponding body handling
  • Fixed the missing resource issue for JSON request overloads (GetJsonAsync, etc)
  • Added the SEARCH verb handling

Full Changelog: restsharp/RestSharp@107.0.3...107.1.1

v107.1.0

Compare Source

v107.0.3

Compare Source

  • Use CharSet from ContentType for decoding the request content. If not specified, use Encoding from RestClientOptions (default utf-8)
  • Finally fixed the ThrowOnAnyError being ignored for unsuccessful calls

v107.0.2

Compare Source

What's Changed

  • #​1686 Reverted to using x-www-form-urlencoded by default unless there's a body or multipart form is set in options
  • #​1687 remedy, added a client option DisableCharset to make servers that don't support charset in Content-Type happier
  • Added generic overloads for adding parameters with the type constrained to struct as part of #​1682 fix
  • Added response headers to RestResponse.ContentHeaders collection #​1684
  • Wrapped request cancellation token and source in using for #​1685

Full Changelog: restsharp/RestSharp@107.0.1...107.0.2

v107.0.1

Compare Source

What's Changed
  • Removed default encoding for header parameters
  • Fixed the issue with URL segment parameter value being cast to string instead of conversion

Full Changelog: restsharp/RestSharp@107.0.0...107.0.1

v107.0.0

Compare Source

First preview release using HttpClient.

Check the initial migration guide.

This release includes major breaking changes:

  • Interface IRestClient is removed, use RestClient class instead
  • Interface IRestRequest is removed, use RestRequest class instead
  • Interface IRestResponse is removed, use RestResponse class instead
  • Most of the client options are now in RestClientOptions as they can't be changed after creating the HttpMessageHandler instance
  • Parameter is now an abstract record. Use specific parameter types like QueryParameter
  • All synchronous methods are gone, use asynchronous methods instead
  • Default JSON serializer is now using System.Text.Json, SimpleJson is gone
  • Support for .NET 4.5 is removed, for legacy .NET Framework use the .NET Standard package

Configuration

📅 Schedule: 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.

@renovate renovate bot force-pushed the renovate/restsharp-112.x branch from 74900e4 to 06c8971 Compare October 4, 2024 17:05
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants