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
How to bypass RubyGems prompts in CI - bundler's executable "bundle" conflicts with ... #5245
Comments
JFYI, |
But that sounds like either RubyGems should just override, or that the I think in general RubyGems cannot assume |
Happy New Year! Don't know if you (or anyone else) have time for this issue, but please see ruby/setup-ruby#224 (comment). Most of this is due to the setup-ruby action installing Bundler 2.3.4. Maybe the best thing to do is update RubyGems for Ruby 2.3 thru 2.5, and just update Bundler for Ruby 2.6 and later. I.think. We may have a fix for the issue with Windows Ruby 3.1.0, which was the original issue... |
Windows - It depends on one's setup, but Windows users may often have two bash shells they can use, one from Git, and one from MSYS2. So, Windows Rubies have two bin files for stdlibs/gems that run from the command line, which includes gem and bundle. One file has a .cmd or .bat extension, the other (the bash one) has no extension. Updating bundler creates a bash script with the shebang line coded to Ruby's actual path. The shipped bash script's shebang uses At present I can't think of any way to fix the issue. Not sure whether to close... |
@MSP-Greg Could you show the |
@eregon Thanks, I reviewed things again, and the issue isn't the above. The following prefixes the normal bash bin files:
I think it was added to allow the bash bin files and the Windows bin files to be the same. It's added in Ruby's |
I didn't have time to have a look at this in detail but this reminded me of #2929, so I rebased it. Maybe it fixes things, can you try? |
Using WIndows Ruby 3.1 on Actions. When trying to perform:
The following error is generated:
When running locally, RubyGems prompts with:
What's the recommended way to bypass the prompt in CI?
This issue is related to:
gem
I will abide by the code of conduct.
The text was updated successfully, but these errors were encountered: