When you see The following have been reloaded with a version change in HPC environments, it means a module has been reloaded with a different version, which is usually normal. However, it can also indicate a dependency conflict caused by loading a module with a dependency that replaces another loaded module’s dependency. As an example, suppose you module load A which depends on module D/2.0. Then you module load B which depends on module D/1.1. You will get the warning and module D/2.0 will be unloaded and replaced by module D/1.1.
Proceeding despite the conflict may result in unexpected behavior, including fatal errors such as segmentation faults. If you come across such a warning within your workflow, it is advisable to consider the possibility of a newer version being available. I recommend checking Anaconda (https://anaconda.org/anaconda/repo) for the latest versions of the required software. If so, try building an Anaconda environment.
Best practice is to use module reset prior to loading modules at the terminal and in sbatch scripts. Do not load modules in your .bashrc file, and only use the defaults or module reset. The goal is to give each job its own separate, clean, reproducible environment to work in.