bundle-lock1
Creates / updates a lockfile without installing
Usage
bundle lock
[--update]
[--bundler
[=BUNDLER]]
[--local]
[--print]
[--lockfile=PATH]
[--full-index]
[--gemfile=GEMFILE]
[--add-checksums]
[--add-platform]
[--remove-platform]
[--normalize-platforms]
[--patch]
[--minor]
[--major]
[--pre]
[--strict]
[--conservative]
Overview
Lock the gems specified in Gemfile.
Options
-
--update[=<list>] -
Ignores the existing lockfile. Resolve then updates lockfile. Taking a list of gems or updating all gems if no list is given.
-
--bundler[=BUNDLER] -
Update the locked version of bundler to the given version or the latest version if no version is given.
-
--local -
Do not attempt to connect to
rubygems.org. Instead, Bundler will use the gems already present in Rubygems' cache or invendor/cache. Note that if a appropriate platform-specific gem exists onrubygems.orgit will not be found.
-
--print -
Prints the lockfile to STDOUT instead of writing to the file system.
-
--lockfile=LOCKFILE -
The path where the lockfile should be written to.
-
--full-index -
Fall back to using the single-file index of all gems.
-
--gemfile=GEMFILE -
Use the specified gemfile instead of [
Gemfile(5)][Gemfile(5)].
-
--add-checksums -
Add checksums to the lockfile.
-
--add-platform=<list> -
Add a new platform to the lockfile, re-resolving for the addition of that platform.
-
--remove-platform=<list> -
Remove a platform from the lockfile.
-
--normalize-platforms -
Normalize lockfile platforms.
-
--patch -
If updating, prefer updating only to next patch version.
-
--minor -
If updating, prefer updating only to next minor version.
-
--major -
If updating, prefer updating to next major version (default).
-
--pre -
If updating, always choose the highest allowed version, regardless of prerelease status.
-
--strict -
If updating, do not allow any gem to be updated past latest --patch | --minor | --major.
-
--conservative -
If updating, use bundle install conservative update behavior and do not allow shared dependencies to be updated.
Updating all gems
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.
Updating a list of gems
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 Gemfile.lock.
For instance, you only want to update nokogiri, run 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 Gemfile.lock.
Supporting other platforms
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.
Options
See bundle update(1) bundle-update.1.html for details.
Releases
6 releases since Debian 9 (Stretch); the text changed 5 times.
--add-checksums since Debian 13 (Trixie);
--add-platform since Debian 10 (Buster);
--bundler since Debian 13 (Trixie);
--conservative since Debian 10 (Buster);
--full-index since Debian 10 (Buster);
--gemfile since Debian 13 (Trixie);
--major since Debian 10 (Buster);
--minor since Debian 10 (Buster);
--normalize-platforms since Debian 13 (Trixie);
--patch since Debian 10 (Buster);
--pre since Debian 13 (Trixie);
--remove-platform since Debian 10 (Buster);
--strict since Debian 10 (Buster).