Faraday (and other gems) showing incorrect incompatibility

[skryukov]

As far as I can see, this issue comes from cached errors. For example, check the Faraday gem:
https://www.railsbump.org/gems/faraday/compatibility/rails-8-0

Look for the line: RailsBump::Checker::BundleLocallyCheck Output: Bundler error: Illformed requirement [">= 2.0, < 3.5"]

The issue occurred in the BundleLocallyCheck service where it passes [">= 2.0, < 3.5"] instead of the correct format [">= 2.0", "< 3.5"]. Service doesn't exist anymore, but the incompatible status is cached.

Additional examples from the main app page:

• https://www.railsbump.org/gems/google-apis-youtubereporting_v1/compatibility/rails-7-2
• https://www.railsbump.org/gems/sbmt-kafka_producer/compatibility/rails-7-2

[erikhSSI]

also rails_admin gem => https://www.railsbump.org/gems/rails_admin/compatibility/rails-7-2

[PapePathe]

Hello here,

Are the any directions on where to start looking if i wanted to volunteer and fix this issue ?

[etagwerker]

@PapePathe Thanks for volunteering! I would check the GitHub project that is running the RailsBump::Checker::BundleLocallyCheck check: https://github.com/railsbump/checker/blob/main/lib/rails_bump/checker/bundle_locally_check.rb

It could be one of 2 things:

• When we are calling the GitHub action we are passing the string as illformed.
• When the GitHub action is trying to run the check, it is improperly generating the dependency string.

[fbuys]

I have an idea, so I'll take a stab at fixing this one

[fbuys]

After some digging I noticed that we already have a PR that fixes this issue railsbump/checker#10
I'll review the PR and see how I can help push it over the finish line.