-
Notifications
You must be signed in to change notification settings - Fork 341
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Relax thor version requirement #816
Conversation
We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story. The labels on this github issue will be updated when the story is started. |
+1 on relaxing the thor version specification. I have multiple dependencies that depend on thor; this license_finder requirement forces my application backwards and in the future it may not be possible. Good luck! |
Hey @nertzy ! I am all for this but the issue comes with the tests. With the changes you made, it looks like some formats may have changed which caused the tests to fail. If you want to touch up the tests with this change we can take a look at how much output would change |
FYI I was playing around with thor today and there has been some changes that break LF. I created an issue here: rails/thor#751. Not sure of the plan to fix this but I think this type of thing is why the version of thor was more restrictive :\ |
It doesn't seem like thor is going to address this problem any time soon. Would it make more sense to stop relying on thor's |
@nertzy Please sign the Contributor License Agreement! Click here to manually synchronize the status of this Pull Request. See the FAQ for frequently asked questions. |
@nertzy Thank you for signing the Contributor License Agreement! |
Is there any intention of fixing this in LicenseFinder since Thor apparently won't change the behavior on their side? From what I can see, depending on Thor < 1.1.0 has the downside of effectively not supporting Ruby 3 (at least the Thor changelog says that 1.1.0 introduced Ruby 3 compatibility and the change to use |
I think it would be a great idea to use I now have a project where I can not upgrade to the latest version of karafka because of the thor version restriction. |
eeaaa99
to
cbf21ce
Compare
2398338
to
8739c6d
Compare
Authored-by: Grant Hutchins <[email protected]>
8739c6d
to
1876856
Compare
What can I do to get this merged? |
Hey @nertzy ! Sorry for the delay on this. I think you are right saying that this is how thor is now and we should probably do something about it. The change will be quite large but I imagine to be trivial to get |
I made a workaround to get this out so we didn't make major changes. #886 will update so the newest thor is used. Gonna close this for now! |
I use license finder on some Ruby projects that also use thor.
I want to be able to upgrade to thor 1.1 on my project, but license finder has a strict 1.0.x version requirement. This relaxes the requirement to 1.x.