conda
Clarify that existing lockfiles are used for relocking
Description
Update documentation to clarify that existing lockfiles are used for relocking.
I wasn't sure where to do this. I ended up copying the basic usage example from README.md to the Github Pages documentation. Let me know what you think.
Deploy Preview for conda-lock ready!
| Name | Link |
|---|---|
| Latest commit | d586bd9c8453582623c5c5dc55c853bd86831a07 |
| Latest deploy log | https://app.netlify.com/sites/conda-lock/deploys/662f7c17cd494c000800fd61 |
| Deploy Preview | https://deploy-preview-632--conda-lock.netlify.app |
| Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
![netlify[bot] avatar](https://avatars.githubusercontent.com/in/13473?v=4 "Published by a pub.dev verified publisher"){kind=small}
@mariusvniekerk, @mariusvniekerk, is this accurate?
I might have missed some updates in recent releases, but I do remember release https://github.com/conda/conda-lock/releases/tag/v2.3.0, where
This release changes the way that old dependencies from previous lockfiles are persisted. In most cases, the new behavior of locking with conda-lock is equivalent to
rm conda-lock.yml && conda-lock.
Good eye @riccardoporreca! To the best of my understanding, it is not accurate, and the old lockfile will only be used for:
- a skipped platform
-
--update
@sfinkens, do you have any evidence to the contrary?
@maresb I just checked again and don't have any evidence. Sorry, my fault. I'll fix that