uv
42bdfcda - Store the resolution fork markers to the lockfile

Commit

325 days ago

Store the resolution fork markers to the lockfile Add the overall list of forks to the lockfiles, so we can use them as preferences to avoid instabilities in the next step. I've ordered the structs so that metadata is on top, and payload at the bottom, as it is in the lockfile itself.

Author

konstin

Committer

konstin

Parents

3252f427

Files16

crates
- uv-resolver/src
  - lock.rs
  - resolution
    - graph.rs
  - resolver
    - resolver_markers.rs
  - snapshots
    - uv_resolver__lock__tests__hash_optional_missing.snap
    - uv_resolver__lock__tests__hash_optional_present.snap
    - uv_resolver__lock__tests__hash_required_present.snap
    - uv_resolver__lock__tests__missing_dependency_source_unambiguous.snap
    - uv_resolver__lock__tests__missing_dependency_source_version_unambiguous.snap
    - uv_resolver__lock__tests__missing_dependency_version_unambiguous.snap
    - uv_resolver__lock__tests__source_direct_has_subdir.snap
    - uv_resolver__lock__tests__source_direct_no_subdir.snap
    - uv_resolver__lock__tests__source_directory.snap
    - uv_resolver__lock__tests__source_editable.snap
- uv/tests
  - branching_urls.rs
  - lock.rs
  - lock_scenarios.rs

uv 42bdfcda - Store the resolution fork markers to the lockfile

uv
42bdfcda - Store the resolution fork markers to the lockfile