ship cross platform lock files to users as a preview feature

[BurntSushi]

This issue tracks progress toward shipping robust cross platform lock files in uv. This is not something that is planned to be added to the uv pip CLI, but rather, as part of the workspace-aware uv. (Which hasn't been built out yet.)

Work items

• cross platform lock file generation #3350
• universal-lock: track version numbers for all distributions #3356
• universal-lock: deal with hashes (or lack there of) for some types of distributions #3357
• iron out how to represent path dependencies in the universal lock file #3506
• universal-lock: clean up lock file format #3611
• write tests specific to universal lock files #3880
• pick some real Python projects and attempt to port them to uv with universal locking #3881
• universal-lock: audit data structures to ensure they can handle multiple versions of the same package #3927
• universal-lock: if we write file paths to a lock file, we need to make them portable #4307
• universal-lock: ignore dependencies that are disjoint with a forked resolver state's marker expressions #4194
• Integrate with uv install.
• Integrate with uv run.
• Build uv update, which updates versions in the lock file.
• Make an assessment on the state of error handling. (e.g., What happens when one fork of the resolver fails but others do not.)
• Tracking issue: Stabilize uv.lock format #4893
• Remove extra duplication from lockfile #4888
• Audit handling of hashes in the lockfile #4924

Non-blocking work items

These shouldn't block shipping the universal resolver, but I thought it'd still be good to track them.

• universal-lock: non-conflicting requirements with non-overlapping marker expressions provoke a fork #4357
• universal-lock: use resolution of a fork as input preferences to its child forks #4617

[BurntSushi]

While not every issue in the list has been completed, uv lock is currently shipping as a preview feature that folks can use. There is still work to do before it leaves "preview," but I think that's better tracked by the release-ready project: https://github.com/orgs/astral-sh/projects/11

[mishamsk]

@BurntSushi hey! thanks for doing all of this. much appreciated! Although I did notice the lock command, I wasn't sure how to use it to force UV to install from lock => landed on this issue to track progress. Now that you've closed it, I was wondering if there is a way for the public to track progress? The project is internal apparently...

[BurntSushi]

@BurntSushi hey! thanks for doing all of this. much appreciated! Although I did notice the lock command, I wasn't sure how to use it to force UV to install from lock => landed on this issue to track progress. Now that you've closed it, I was wondering if there is a way for the public to track progress? The project is internal apparently...

I think you want uv sync.

Apologies about the project being private. I didn't realize that. We're working on fixing that (or publishing some other way to track progress).

[mishamsk]

I think you want uv sync.

ah, yes, how did I miss that. awesome, thanks! couldn't find some feature-tracking issue, but given your other comment - I'll just continue checking issues for now. thanks!

[charliermarsh]

The project should be public now: https://github.com/orgs/astral-sh/projects/11

[charliermarsh]

(Thanks, it wasn't intended to be private, glad you pointed that out.)