You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Several things are fixed:
* Don't re-install a plugin referenced from the gemfile with every
call to `bundle install`
* If the version of a plugin referenced in the gemfile conflicts
with what's in the plugin index, _do_ re-install it
* If plugins aren't installed yet, don't throw cryptic errors from
commands that don't implicitly install gems, such as
`bundle check` and `bundle info`. This also applies if the
plugin index references a system gem, and that gem is removed.
This is all accomplished by actuallying including plugins as
regular dependencies in the Gemfile, so that they end up in the
lockfile, and then just using the regular lockfile with the
plugins-only pass of the gemfile in the Plugin infrastructure.
This also means that non-specific version constraints can be
used for plugins, and you can update them with
`bundle update <plugin>` just like any other gem.
Co-authored-by: Diogo Fernandes <diogofernandesop@gmail.com>
\fBplugins_in_lockfile\fR (\fBBUNDLE_PLUGINS_IN_LOCKFILE\fR): Include plugins as regular dependencies in the lockfile\.
167
+
.IP"\(bu"4
166
168
\fBprefer_patch\fR (BUNDLE_PREFER_PATCH): Prefer updating only to next patch version during updates\. Makes \fBbundleupdate\fR calls equivalent to \fBbundlerupdate\-\-patch\fR\.
167
169
.IP"\(bu"4
168
170
\fBprint_only_version_number\fR (\fBBUNDLE_PRINT_ONLY_VERSION_NUMBER\fR): Print only version number from \fBbundler\-\-version\fR\.
0 commit comments