Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add forks to lockfile, don't read them yet #5480

Merged
merged 3 commits into from
Jul 30, 2024
Merged

Add forks to lockfile, don't read them yet #5480

merged 3 commits into from
Jul 30, 2024

Commits on Jul 30, 2024

  1. 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.
    @konstin
    konstin committed Jul 30, 2024
    Configuration menu
    Copy the full SHA
    f008aa9 View commit details
    Browse the repository at this point in the history

  2. Store the fork markers of diverging versions in uv.lock 

    To set the preferences correctly, we need to know which version belongs to which fork. Instead of tracing that through the graph, we save this information in the lockfile to indicate to the user how and why there are multiple version for a package.
    @konstin
    konstin committed Jul 30, 2024
    Configuration menu
    Copy the full SHA
    fd78f72 View commit details
    Browse the repository at this point in the history

  3. Add fork preferences to ResolverMarkers::Universal 

    This gives the resolver access to the fork preferences from the lockfile.
    @konstin
    konstin committed Jul 30, 2024
    Configuration menu
    Copy the full SHA
    4b1ca1f View commit details
    Browse the repository at this point in the history