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.

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

Incremental lockfile updates #4

Closed
baszalmstra opened this issue May 5, 2023 · 2 comments · Fixed by #140
Closed

Incremental lockfile updates #4

baszalmstra opened this issue May 5, 2023 · 2 comments · Fixed by #140

Comments

@baszalmstra
Copy link
Contributor

When the lockfile is out of date it is completely regenerated. We should change this behavior so that the content of the previous lockfile resides in the SolverTask::locked_packages. This will make sure that package versions remain stable unless this would result in an unsolvable situation.

@baszalmstra baszalmstra added this to the v0.1.0 milestone May 5, 2023
@ruben-arts ruben-arts removed this from the v0.1.0 Initial public release milestone May 25, 2023
@baszalmstra
Copy link
Contributor Author

This requires the ability to reconstruct a PackageRecord from a lock file (#6)

@baszalmstra
Copy link
Contributor Author

This has been done in #129 and tested in #140

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants