[KongchangAI]
Conceptuv lock file

uv.lock

A lock file generated by the uv tool that records the exact versions, source hashes and platform markers of all project dependencies. It is used to achieve reproducible installations.

Core Facts

Timeline (last 90 days)

Nov 2

The design of uv.lock is an advantage in application projects (ensuring reproducibility), but in library projects it causes a version-freezing effect, with side effects outweighing the benefits.

Unverified50%
Nov 2

By convention, Python library projects should not include a uv.lock file, because pinning versions affects downstream projects; therefore a library project's uv.lock is usually written into .gitignore.

Unverified50%
Nov 2

When running commands such as uv run pytest, uv automatically generates a uv.lock file if the lock file is missing.

Unverified50%
Nov 2

The role of uv.lock is to precisely record the versions, source hashes, and platform markers of all direct and transitive dependencies of a project, so as to achieve reproducible installation across machines and over time.

Unverified50%
Nov 2

In a library project, if uv.lock pins old dependency versions from before Python 3.15 support, deleting uv.lock causes uv to re-resolve dependencies and choose new versions that support Python 3.15, thereby resolving the build error.

Unverified50%
Nov 2

When dependencies need to be reproduced precisely in a production environment, deleting the lock file may mask problems, and this rule does not apply.

Unverified50%
Oct 19

Using lock files such as uv.lock can prevent unexpected changes introduced by automatic upgrades.

Unverified50%
Oct 16

Lockfiles (such as pnpm-lock.yaml, package-lock.json, yarn.lock) record every dependency actually installed by the project and its exact version; when a direct dependency requires a higher version, the package manager will bump the lockfile entry, which may trigger synchronized changes in indirect dependencies.

Verified75%
Oct 8

uv.lock is a lock file generated by the Python package manager uv that precisely records the specific versions of all dependency packages in the current environment.

Unverified50%
Oct 8

When the package version declared in pyproject.toml drifts from the record in the lock file, it may cause inconsistent behavior between local and CI environments.

Unverified50%

1 more timeline events

All Facts (11)

Verified

Lockfiles (such as pnpm-lock.yaml, package-lock.json, yarn.lock) record every dependency actually installed by the project and its exact version; when a direct dependency requires a higher version, the package manager will bump the lockfile entry, which may trigger synchronized changes in indirect dependencies.

75%
Unverified

The design of uv.lock is an advantage in application projects (ensuring reproducibility), but in library projects it causes a version-freezing effect, with side effects outweighing the benefits.

50%
Unverified

When running commands such as uv run pytest, uv automatically generates a uv.lock file if the lock file is missing.

50%
Unverified

The role of uv.lock is to precisely record the versions, source hashes, and platform markers of all direct and transitive dependencies of a project, so as to achieve reproducible installation across machines and over time.

50%
Unverified

In a library project, if uv.lock pins old dependency versions from before Python 3.15 support, deleting uv.lock causes uv to re-resolve dependencies and choose new versions that support Python 3.15, thereby resolving the build error.

50%
Unverified

When dependencies need to be reproduced precisely in a production environment, deleting the lock file may mask problems, and this rule does not apply.

50%
Unverified

By convention, Python library projects should not include a uv.lock file, because pinning versions affects downstream projects; therefore a library project's uv.lock is usually written into .gitignore.

50%
Unverified

Using lock files such as uv.lock can prevent unexpected changes introduced by automatic upgrades.

50%
Unverified

When the package version declared in pyproject.toml drifts from the record in the lock file, it may cause inconsistent behavior between local and CI environments.

50%
Unverified

uv.lock is a lock file generated by the Python package manager uv that precisely records the specific versions of all dependency packages in the current environment.

50%
Unverified

v1.12.1 aligns the package version with the record in uv.lock, which is a normative correction for internal dependency management.

50%

Source Articles