chore(deps): bump faraday from 2.14.2 to 2.14.3

[dependabot]

Bumps faraday from 2.14.2 to 2.14.3.

Release notes

Sourced from faraday's releases.

v2.14.3

Security Note

This release contains a security fix, we recommend all users to upgrade as soon as possible. A Security Advisory with more details will be posted shortly.

What's Changed

• Upgrade CI lint step from Ruby 3 to 4 by @​larouxn in lostisland/faraday#1673
• feat(test): add Stubs#clear to remove all stubs by @​SAY-5 in lostisland/faraday#1675

New Contributors

• @​SAY-5 made their first contribution in lostisland/faraday#1675

Full Changelog: lostisland/faraday@v2.14.2...v2.14.3

Commits

• f1ace87 Version bump to 2.14.3
• 36764bf Merge commit from fork
• 59334e0 feat(test): add Stubs#clear to remove all stubs (#1675)
• 469f25c Upgrade CI lint step from Ruby 3 to 4 (#1673)
• See full diff 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)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[mergify]

Queued — the merge queue status continues in this comment ↓.

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-06-22 07:18 UTC · Rule: dependabot
• 🟠 Checks running · on draft merge queue: queuing main (8a2a5dc), #1188, #1189 and #1186 together #1192
• 🚫 Left the queue — 2026-06-22 07:20 UTC · at 29b345b71b430fdb5334f9538f645c374519edff

This pull request spent 2 minutes 13 seconds in the queue, including 49 seconds running CI.

Required conditions to merge

• author=dependabot[bot]
  • chore(deps): bump faraday from 2.14.2 to 2.14.3 #1186
• base=main
• status-success=build
• any of [🛡 GitHub repository ruleset rule main]:
  • check-success = build
  • check-neutral = build
  • check-skipped = build
• any of [🛡 GitHub repository ruleset rule main]:
  • check-success = lint
  • check-neutral = lint
  • check-skipped = lint

Reason

Pull request #1186 has been dequeued

The pull request has been closed manually

Hint

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

Tick the box to put this pull request back in the merge queue (same as @mergifyio queue).

• Requeue this pull request

[dependabot]

Looks like faraday is up-to-date now, so this is no longer needed.