Say my project has the following files
environment.yml
virtual-packages.yml
conda-linux-64.lock
conda-lock.yml
I want to add 1 new package with minimum required version updates to other packages similar to doing conda install in an existing environment. My assumption was that I could update environment.yml with the new package and then do the following:
conda-lock lock --update <new_package_name>
however this seems to trigger a full re-solve that bumps the version for all packages in environment
If I dont modify the environment.yml and run conda-lock lock --update <new_package_name> conda-lock will still re-solve the environment but it will fail to include the new package.
Is this a bug or is there something I am missing?
Say my project has the following files
I want to add 1 new package with minimum required version updates to other packages similar to doing conda install in an existing environment. My assumption was that I could update environment.yml with the new package and then do the following:
conda-lock lock --update <new_package_name>however this seems to trigger a full re-solve that bumps the version for all packages in environment
If I dont modify the environment.yml and run
conda-lock lock --update <new_package_name>conda-lock will still re-solve the environment but it will fail to include the new package.Is this a bug or is there something I am missing?