Closed jaimergp closed 3 years ago
Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe
) and found it was in an excellent condition.
You can just delete the other migrators.
That implies that users that need to opt-in would switch to a all-manual mode they need to take care of, right?
Replacing the 11.1/11.2 migrator with the current conda_build_config
(which contains more comments than usual) seems to work.
That implies that users that need to opt-in would switch to a all-manual mode they need to take care of, right?
Yes. I wouldn't worry about it being all-manual until a maintainer comes forward who says they need the older versions.
Thanks Jaime! 😄
MNT: Re-rendered with conda-build 3.20.5, conda-smithy 3.8.6, and conda-forge-pinning 2021.02.16.21.37.58
Checklist
0
(if the version changed)conda-smithy
(Use the phrase code>@<space/conda-forge-admin, please rerender in a comment in this PR for automated rerendering)One of the premises for shrinking the CUDA matrix as part of https://github.com/conda-forge/conda-forge-pinning-feedstock/pull/1162 was that the maintainer could opt-in for more versions using
conda_build_config.yaml
. I have added what I think should be the full file (and that we will eventually link in the docs), but sinceconda-smithy
applies the migrators afterconda_build_config
it has no effect: the migrator shadows the changes.Is this something we need to address in
conda-smithy
?