list of references, as a string, or a yaml list (abbreviated or full as yaml items). All the root nodes will be in the same dependency graph, leading to conflicts if they depend on different versions of directly defined in the command line. • It encodes a graph, not just a list of versions, as different nodes in the graph might be using different versions too. • The options values at each package. As downstream it is important that this information is also stored, so it is also possible to build intermediate nodes of the graph leading to the same result. 9.4. Lockfiles 117 Conan Documentation, Release 1.23.0

list of references, as a string, or a yaml list (abbreviated or full as yaml items). All the root nodes will be in the same dependency graph, leading to conflicts if they depend on different versions of directly defined in the command line. • It encodes a graph, not just a list of versions, as different nodes in the graph might be using different versions too. • The options values at each package. As downstream it is important that this information is also stored, so it is also possible to build intermediate nodes of the graph leading to the same result. 9.4. Lockfiles 117 Conan Documentation, Release 1.24.1

list of references, as a string, or a yaml list (abbreviated or full as yaml items). All the root nodes will be in the same dependency graph, leading to conflicts if they depend on different versions of directly defined in the command line. • It encodes a graph, not just a list of versions, as different nodes in the graph might be using different versions too. • The options values at each package. As downstream it is important that this information is also stored, so it is also possible to build intermediate nodes of the graph leading to the same result. 9.4. Lockfiles 125 Conan Documentation, Release 1.27.1

list of references, as a string, or a yaml list (abbreviated or full as yaml items). All the root nodes will be in the same dependency graph, leading to conflicts if they depend on different versions of directly defined in the command line. • It encodes a graph, not just a list of versions, as different nodes in the graph might be using different versions too. • The options values at each package. As downstream it is important that this information is also stored, so it is also possible to build intermediate nodes of the graph leading to the same result. 9.4. Lockfiles 113 conan Documentation, Release 1.17.2

list of references, as a string, or a yaml list (abbreviated or full as yaml items). All the root nodes will be in the same dependency graph, leading to conflicts if they depend on different versions of directly defined in the command line. • It encodes a graph, not just a list of versions, as different nodes in the graph might be using different versions too. • The options values at each package. As downstream it is important that this information is also stored, so it is also possible to build intermediate nodes of the graph leading to the same result. 9.4. Lockfiles 117 Conan Documentation, Release 1.22.3

list of references, as a string, or a yaml list (abbreviated or full as yaml items). All the root nodes will be in the same dependency graph, leading to conflicts if they depend on different versions of the lockfile: 128 Chapter 9. Versioning Conan Documentation, Release 1.29.2 { "graph_lock": { "nodes": { "0": { "ref": "pkgb/0.1@user/testing", "options": "shared=False", "requires": ["1"], "path": kgb_ ˓→base.lock --base Let’s inspect the locks/pkgb_base.lock lockfile: { "graph_lock": { "nodes": { "0": { "ref": "pkgb/0.1@user/testing", "requires": ["1"], "path": "..\\conanfile.py", "context":

list of references, as a string, or a yaml list (abbreviated or full as yaml items). All the root nodes will be in the same dependency graph, leading to conflicts if they depend on different versions of lockfile: 132 Chapter 10. Versioning Conan Documentation, Release 1.30.2 { "graph_lock": { "nodes": { "0": { "ref": "pkgb/0.1@user/testing", "options": "shared=False", "requires": ["1"], "path": kgb_ ˓→base.lock --base Let’s inspect the locks/pkgb_base.lock lockfile: { "graph_lock": { "nodes": { "0": { "ref": "pkgb/0.1@user/testing", "requires": ["1"], "path": "..\\conanfile.py", "context":

list of references, as a string, or a yaml list (abbreviated or full as yaml items). All the root nodes will be in the same dependency graph, leading to conflicts if they depend on different versions of lockfile: 132 Chapter 10. Versioning Conan Documentation, Release 1.31.4 { "graph_lock": { "nodes": { "0": { "ref": "pkgb/0.1@user/testing", "options": "shared=False", "requires": ["1"], "path": kgb_ ˓→base.lock --base Let’s inspect the locks/pkgb_base.lock lockfile: { "graph_lock": { "nodes": { "0": { "ref": "pkgb/0.1@user/testing", "requires": ["1"], "path": "..\\conanfile.py", "context":

list of references, as a string, or a yaml list (abbreviated or full as yaml items). All the root nodes will be in the same dependency graph, leading to conflicts if they depend on different versions of directly defined in the command line. • It encodes a graph, not just a list of versions, as different nodes in the graph might be using different versions too. • The options values at each package. As downstream it is important that this information is also stored, so it is also possible to build intermediate nodes of the graph leading to the same result. 9.4. Lockfiles 121 Conan Documentation, Release 1.25.2

list of references, as a string, or a yaml list (abbreviated or full as yaml items). All the root nodes will be in the same dependency graph, leading to conflicts if they depend on different versions of directly defined in the command line. • It encodes a graph, not just a list of versions, as different nodes in the graph might be using different versions too. • The options values at each package. As downstream it is important that this information is also stored, so it is also possible to build intermediate nodes of the graph leading to the same result. 9.4. Lockfiles 125 Conan Documentation, Release 1.26.1