How ranges become one verified, reproducible dependency graph.
Resolution, installation, and locking
Supported ranges
- Exact versions, caret ranges, tilde ranges, and comparator sets such as >=1.2,<2.0.
- Prerelease versions match only when the declared range itself names a prerelease.
- A backtracking resolvelib provider searches for one compatible version per package name.
What the lockfile guarantees
dvlib.lock is JSON and records the selected version, SHA-256 digest, dependency edges, and whether a package entered through root development dependencies. Commit it when consumers need repeatable resolution.
Cache does not bypass integrity
Package tarballs are cached globally under ~/.cache/dvlib, but every use is checked against the registry or lockfile SHA-256. A cached archive is not trusted merely because it already exists.
Install versus update
| Command | Resolution behavior |
|---|---|
| dvlib install | Reuses compatible lockfile pins and fills any missing packages. |
| dvlib update | Refreshes every locked package within declared ranges. |
| dvlib update NAME | Refreshes one selected locked package while retaining other pins where possible. |
| dvlib outdated | Reports newer non-yanked versions that still satisfy root ranges. |