-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Fastlane installation is broken due to rdoc 6.3.1 version #18642
Comments
It seems like you have not included the output of |
It's interesting🤔 I could replicate the same on macOS (11.3.1). I'll look into this. |
I can't find the tag for 6.3.1 on https://github.com/ruby/rdoc but this seems to be the diff between the two versions https://my.diffend.io/gems/rdoc/6.3.0/6.3.1 This is where actually crashed https://my.diffend.io/gems/rdoc/6.3.0/6.3.1#d2h-891029-4251 It seems that this In the meantime, as @LeonidLapshin suggests using older |
Reported the issue here |
rdoc seemed to be fixed. I hope we'll see a new release within a couple of days🤞 |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Friendly reminder: contributions are always welcome! Check out CONTRIBUTING.md for more information on how to help with This issue will be auto-closed if there is no reply within 1 month. |
New rdoc version is finally released and therefore this issue can be closed. Maybe @LeonidLapshin can confirm it too? |
rdoc 6.3.2 works for me |
New Issue Checklist
Issue Description
Fastlane installation is broken since Sunday on Ubuntu 20.
Rdoc 6.3.1 breaks fastlane installation, manual installation 6.3.0 rdoc version before fastlane installation works well and fastlane installation succeeds.
Command executed
gem install fastlane
Complete output when running fastlane, including the stack trace and command used
The text was updated successfully, but these errors were encountered: