Bump req from 0.4.14 to 0.5.1

[dependabot]

Bumps req from 0.4.14 to 0.5.1.

Changelog

Sourced from req's changelog.

v0.5.1 (2024-06-24)

• [retry]: Default :retry_log_level to :warning

• [put_path_params]: Add :path_params_style option

• [put_aws_sigv4]: Fix path encoding

• [decode_body]: Improve tar detection

• [run_finch]: Fix defaulting to using just HTTP/1

v0.5.0 (2024-05-28)

Req v0.5.0 brings testing enhancements, errors standardization, %Req.Response.Async{}, and more improvements and bug fixes.

Testing Enhancements

In previous releases, we could only create test stubs (using [Req.Test.stub/2]), that is, fake HTTP servers which had predefined behaviour. Let's say we're integrating with a third-party weather service and we might create a stub for it like below:

Req.Test.stub(MyApp.Weather, fn conn ->
  Req.Test.json(conn, %{"celsius" => 25.0})
end)

Anytime we hit this fake we'll get the same result. This works extremely well for simple integrations however it's not quite enough for more complicated ones. Imagine we're using something like AWS S3 and we test uploading some data and reading it back again. While we could do this:

Req.Test.stub(MyApp.S3, fn
  conn when conn.method == "PUT" ->
    # ...
conn when conn.method == "GET" ->
# ...
end)

making the test just a little bit more thorough will make it MUCH more complicated, for example: the first GET request should return a 404, we then make a PUT, and now GET should return a 200. We could solve it by adding some state to our test (e.g. an agent) but there is a simpler way and that is to set request expectations using the new [Req.Test.expect/3] function:

Req.Test.expect(MyApp.S3, fn conn when conn.method == "GET" ->
</tr></table> 

... (truncated)

Commits

• 84308db Release v0.5.1
• af1a34f run_finch: Fix defaulting to using just HTTP/1
• 7148e42 Improve test
• b6f542c Remove TODO
• e893132 decode_body: Improve tar detection
• db53ac4 Update CHANGELOG
• deae87c put_aws_sigv4: Fix path encoding (#374)
• a7ce008 Fix run!/2 specs
• 59f4ea0 Update docs
• 3c1319c Update docs
• Additional 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 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)

[dependabot]

Superseded by #48.