Nick Charlton

I'm currently stuck on understanding why Ruby 2.6, 2.7 and 3.2 fail. The 2.* series are the same reason, but 3.2 is close but not completely the same. I'm also...

Yeah, I suspect I will end up doing that. It's definitely not worth too much effort, even for a library where I want to make things easier for folks. I'm...

It's hard to put a timeline to it, unfortunately. I'm dipping into when I can find a bit of time/inspiration on what might be causing the tests to fail on...

I've started looking at the deprecation warnings, with the hope that this either solves our CI problem or indicates what it might be, starting with: * #207 * #208 *...

Yeah, I think that's exactly the problem we're facing. I'd like to identify the lowest-possible Bundler release we can target and then start testing from that release onwards. If anyone...

@kyrofa, I think a tool like Appraisal should support as wide a set of Ruby versions as possible so unless it becomes clearly prohibitive to keep supporting, 2.5 will stay....

@kyrofa is right — it's GitHub Actions/CI that's the main problem right now. That said, anything you could do to help with the deprecation warnings would be excellent, too. I...

Sorry, @Maimer, I missed your question. I've been having a generally better time with GitHub Actions (although, I dislike the centralisation on a single service). Something I'd seen a lot...

Alas, no. I've not managed to find any time to go back to investigating the outstanding problems — which is partly been because of some more intense client project time...

I've just [released v2.5.0](https://github.com/thoughtbot/appraisal/releases/tag/v2.5.0), which at least ships everything done so far and should fix a lot of the recent bug reports.