chore(deps): bump req from 0.6.3 to 0.7.3

[dependabot]

Bumps req from 0.6.3 to 0.7.3.

Release notes

Sourced from req's releases.

v0.7.3

• encode_body: Revert "Automatically change GET to POST when request body is set."

v0.7.2

• encode_body: Bring back form_multipart: [{string_name, value}].
• put_aws_sigv4: Fix AWS SigV4 compatibility with Supabase Storage S3.

Changelog

Sourced from req's changelog.

v0.7.3 (2026-08-19)

v0.7.2 (2026-07-31)

• encode_body: Bring back form_multipart: [{string_name, value}].
• [put_aws_sigv4]: Fix AWS SigV4 compatibility with Supabase Storage S3.

v0.7.1 (2026-07-28)

• Deprecate cache: true/cache step. It will be removed in Req v0.8. I plan a comprehensive cache solution for Req v1.0+.

v0.7.0 (2026-07-28)

• [Req]: Add Req.new(req, options).

• [Req]: Treat URL userinfo as Basic Authentication.

• [Req], [Req.Request]: Deprecate adapter: fun in favour of adapter: mod.

• [Req.Request]: (BREAKING CHANGE) Remove current_request_steps field.

• [Req.Request]: Fix redacting remaining auth values.

• (BREAKING CHANGE) Replace run_finch step with [Req.Finch] adapter module.

• (BREAKING CHANGE) Replace put_plug and run_plug steps with [Req.Plug] adapter module.

• [Req.Finch]: Support finch: options.

• [Req.Finch]: Support :request_timeout.

• [Req.Finch]: Fix handling duplicate response headers.

• [Req.Finch]: Deprecate finch: name in favour of finch: [name: name].

• [Req.Finch]: Deprecate pool_timeout: value in favour of finch: [pool_timeout: value].

• [Req.Finch]: Deprecate pool_max_idle_time: value in favour of finch: [pool_max_idle_time: value].

• [Req.Finch]: Deprecate :finch_request.

• [Req.Plug]: Handle individual response body chunks.

• [Req.Plug]: Support non-UTF8 request params.

• [Req.Plug]: Put original request private data in conn.private.

• [Req.Test]: Allow descendant processes.

... (truncated)

Commits

• 2901181 Release v0.7.3
• e857078 Revert "encode_body: Automatically change GET to POST when request body is ...
• c136357 Release v0.7.2
• e9d4ebc Fix AWS SigV4 compatibility with Supabase Storage S3 (#498)
• 168a11e Release v0.7.1
• a9c24a1 Deprecate cache: true/cache step
• 6a4f305 Release v0.7.0
• d770830 Hide body: fun for now
• e450b25 Update CI
• 8123419 Fix flaky httpc into: fun test
• 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 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)

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 duplication

Metric	Results
Duplication	0

View in Codacy

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

_{TIP This summary will be updated as you push new changes.}

[codacy-production]

Pull Request Overview

This PR updates the 'req' HTTP client to version 0.7.3. While Codacy indicates the PR is up to standards, there is a critical functional gap: version 0.7.0 of 'req' introduced breaking changes that deprecate step-based adapters in favor of module-based adapters (e.g., migrating from 'run_finch' to 'Req.Finch').

No evidence of these required code migrations exists in the current diff. Unless the project uses only the most basic features of 'req', this update will likely cause runtime exceptions in environments utilizing Finch or Plug adapters. It is recommended to address these breaking changes before merging.

About this PR

• The update to 'req' 0.7.x introduces breaking changes. Specifically, the 'run_finch', 'put_plug', and 'run_plug' steps have been replaced by the 'Req.Finch' and 'Req.Plug' adapter modules. Additionally, the 'current_request_steps' field in 'Req.Request' has been removed. Logic relying on these features must be migrated to avoid runtime errors.

Test suggestions

• Confirm dependency resolution for 'req' version 0.7.3 in mix.lock.
• Verify that HTTP requests using Finch continue to work after migrating from 'run_finch' to the 'Req.Finch' adapter.
• Verify that HTTP requests using Plug for testing/mocking continue to work after migrating from 'run_plug' to the 'Req.Plug' adapter.

Prompt proposal for missing tests

Consider implementing these tests if applicable:
1. Confirm dependency resolution for 'req' version 0.7.3 in mix.lock.
2. Verify that HTTP requests using Finch continue to work after migrating from 'run_finch' to the 'Req.Finch' adapter.
3. Verify that HTTP requests using Plug for testing/mocking continue to work after migrating from 'run_plug' to the 'Req.Plug' adapter.

_{TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback}

[hyperpolymath]

Approved by Antigravity