Hey @expeehaa,

Thanks for the change here. I'm still trying to work out my thoughts on how we handle this; you make a good point about the noise.

If you're using Faraday >= 2.x the gem file specifies that faraday-multipart and faraday-retry should be dependencies

Meaning that you'd have to use the middleware (built-in) for retry if you were using @ >= 1.20 (I belive) and < 2. Or you would use the separate retry gem if you were >= 2.x - I can see how that implementation is confusing.

In either case, we should probably require retry either through the middleware or with the separate gem - but the support and implementation has to be conditional. The reason is, we don't know which one is being used - which is why you get the warning.

I'm am currently at a loss as to how to handle this better. Removing support for Faraday v1 seems like a bit of a drastic change (we cap the version at 3.x) - this is a bit of a precursor to that. I'm going to chat with @kfcampbell about this as well to see if we can come up with a solution, I just really do not have a good one right now.

A note about your change that is orthogonal to our discussion here:

Specifically, on this change, you'll need to suppress the cop exception by adding:
- 'lib/octokit/default.rb'

To the SupressedException list in this file: .rubocop_todo.yml

Or restructure the loading of the gem some other way.

👋 Hey Friends, this pull request has been automatically marked as stale because it has no recent activity. It will be closed if no further activity occurs. Please add the Status: Pinned label if you feel that this issue needs to remain open/active. Thank you for your contributions and help in keeping things tidy!