1BUNDLE-LOCK(1)                                                  BUNDLE-LOCK(1)
2
3
4

NAME

6       bundle-lock - Creates / Updates a lockfile without installing
7

SYNOPSIS

9       bundle    lock   [--update]   [--local]   [--print]   [--lockfile=PATH]
10       [--full-index] [--add-platform] [--remove-platform] [--patch] [--minor]
11       [--major] [--strict] [--conservative]
12

DESCRIPTION

14       Lock the gems specified in Gemfile.
15

OPTIONS

17       --update=<*gems>
18              Ignores  the  existing  lockfile. Resolve then updates lockfile.
19              Taking a list of gems or updating all gems if no list is given.
20
21       --local
22              Do not attempt to connect to rubygems.org. Instead, Bundler will
23              use  the  gems  already  present  in  Rubygems´ cache or in ven‐
24              dor/cache. Note that if a appropriate platform-specific gem  ex‐
25              ists on rubygems.org it will not be found.
26
27       --print
28              Prints  the  lockfile  to  STDOUT instead of writing to the file
29              system.
30
31       --lockfile=<path>
32              The path where the lockfile should be written to.
33
34       --full-index
35              Fall back to using the single-file index of all gems.
36
37       --add-platform
38              Add a new platform to the lockfile, re-resolving for  the  addi‐
39              tion of that platform.
40
41       --remove-platform
42              Remove a platform from the lockfile.
43
44       --patch
45              If updating, prefer updating only to next patch version.
46
47       --minor
48              If updating, prefer updating only to next minor version.
49
50       --major
51              If updating, prefer updating to next major version (default).
52
53       --strict
54              If  updating,  do  not  allow  any gem to be updated past latest
55              --patch | --minor | --major.
56
57       --conservative
58              If updating, use bundle install conservative update behavior and
59              do not allow shared dependencies to be updated.
60

UPDATING ALL GEMS

62       If  you  run  bundle  lock  with  --update option without list of gems,
63       bundler will ignore any previously installed gems and resolve  all  de‐
64       pendencies  again based on the latest versions of all gems available in
65       the sources.
66

UPDATING A LIST OF GEMS

68       Sometimes, you want to update a single gem in the Gemfile(5), and leave
69       the  rest  of the gems that you specified locked to the versions in the
70       Gemfile.lock.
71
72       For instance, you only want to update nokogiri, run bundle  lock  --up‐
73       date nokogiri.
74
75       Bundler will update nokogiri and any of its dependencies, but leave the
76       rest of the gems that you specified locked to the versions in the  Gem‐
77       file.lock.
78

SUPPORTING OTHER PLATFORMS

80       If  you want your bundle to support platforms other than the one you´re
81       running locally, you can run bundle lock --add-platform PLATFORM to add
82       PLATFORM  to the lockfile, force bundler to re-resolve and consider the
83       new platform when picking gems, all without needing to have  a  machine
84       that matches PLATFORM handy to install those platform-specific gems on.
85
86       For a full explanation of gem platforms, see gem help platform.
87

PATCH LEVEL OPTIONS

89       See bundle update(1) bundle-update.1.html for details.
90
91
92
93                                 February 2023                  BUNDLE-LOCK(1)
Impressum