bundle-lock - Creates / Updates a lockfile without installing
bundle lock[--update] [--local] [--print] [--lockfile=PATH] [--full-index] [--add-platform] [--remove-platform] [--patch] [--minor] [--major] [--strict] [--conservative]
Lock the gems specified in Gemfile.
rubygems.org. Instead, Bundler will use the gems already present in Rubygems' cache or in
vendor/cache. Note that if a appropriate platform-specific gem exists on
rubygems.orgit will not be found.
If you run
bundle lock with
--update option without list of gems, bundler will
ignore any previously installed gems and resolve all dependencies again based
on the latest versions of all gems available in the sources.
Sometimes, you want to update a single gem in the Gemfile(5), and leave the rest of
the gems that you specified locked to the versions in the
For instance, you only want to update
bundle lock --update nokogiri.
Bundler will update
nokogiri and any of its dependencies, but leave the rest of the
gems that you specified locked to the versions in the
If you want your bundle to support platforms other than the one you're running
locally, you can run
bundle lock --add-platform PLATFORM to add PLATFORM to
the lockfile, force bundler to re-resolve and consider the new platform when
picking gems, all without needing to have a machine that matches PLATFORM handy
to install those platform-specific gems on.
For a full explanation of gem platforms, see
gem help platform.
See bundle update(1) for details.