Which of the following is NOT one of the actions that triggers re-resolution of Conda lock files?

The action that does not trigger re-resolution of Conda lock files is modifying the build.gradle file. This file is associated with Gradle, which is a build automation tool primarily used for Java projects, and it does not directly interact with Conda or its environment management processes.

Conda lock files are specific to Conda environments and are designed to capture the precise package versions and dependencies at a given point in time. Re-resolution of these files is typically triggered by actions that directly affect the environment and its dependencies.

For instance, running Task Runner can initiate processes that may alter the package environment, potentially requiring an update in the lock file. Similarly, adding a new branch to the repository could involve changes in dependencies, leading to a need for re-resolution. Changes in the list of packages specified in meta.yaml directly affect the packages and their versions, which is fundamental for the lock file’s integrity.

In contrast, while modifications in build.gradle might influence the Java project's build process, they do not have an impact on the Conda environment configuration or behavior regarding locks, hence they do not trigger a re-resolution of Conda lock files.