What triggers re-resolution of Conda lock files in Foundry's Code Repositories? Choose three.

The re-resolution of Conda lock files in Foundry's Code Repositories is triggered by specific changes in the environment or configuration. When upgrading to a newer template version, the environment’s configuration may be updated, necessitating a new resolution of dependencies to ensure compatibility with the new template standards or requirements. This process ensures that all necessary packages and their versions are accurately captured in the lock files to match the updated environment.

Additionally, changing the list of packages in the meta.yaml file also contributes to this need for re-resolution. Whenever the list of required packages is modified, Conda must examine the existing dependencies and potentially update the lock files to reflect these changes accurately. This guarantees that the environment maintains the correct versions of packages needed for the code to function optimally.

While running Task Runner can initiate various tasks within Foundry, it does not inherently trigger the re-resolution of Conda lock files in the same way that upgrading templates or modifying package lists does. Similarly, adding a new branch to the repository typically concerns version control rather than directly influencing the dependency resolution process. These actions would not necessitate a re-evaluation of the lock files because they do not alter the fundamental dependencies that are captured therein.