-
-
Notifications
You must be signed in to change notification settings - Fork 228
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
gems.rb and gems.locked #325
Comments
I've just seen there's an aging PR on this. It may not be the Holy Grail, but given Bundler has a major deprecation warning for the old |
I haven't seen any deprecation warnings yet and there isn't any immediate plans to remove |
I wrote that in a kinda misleading way: Bundler is not deprecating The advantage of (Btw, there's also a typo since I wouldn't highlight this if there were an easy workaround (other than falling back to the ole
|
Take a look at the gems_locked_support branch. |
@postmodern Great, looking good! There's just a tiny thing I'd change: LOCK_FILES = %w[Gemfile.lock gems.locked] Maybe better flip the two since Bundler uses |
I did some tests and discovered that bundler 2.3.6 would prefer |
Weird, another inconsistency of Bundler since the warning suggests otherwise. Never mind, having both is bad to begin with. |
It would be great if this useful gem supported the alternative gemfile names as well:
gems.rb
(alternative forGemfile
)gems.locked
(alternative forGemfile.lock
)These alternative names were introduced in 2017.
The text was updated successfully, but these errors were encountered: