Closed danielhollas closed 3 months 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.
@conda-forge-admin, please rerender
@bollwyvl thank you for merging and for catching the pyteat version update.
I believe this should be backported to version 2.14.0 as well. Let me know if you want me to submit a PR for this. In this case I think one needs to create an extra branch to release from, if I understand the process correctly.
Historical branches are a fair amount of work, and usually only worth it for long-lived things, and then solver might (even now) pick the older revs: a conda-forge-repodata-patches PR for the two affected releases is likely to get better results... will gin something up.
a conda-forge-repodata-patches PR for the two affected releases is likely to get better results... will gin something up.
Ah, that is interesting, I didn't know about this option, thanks! Feel free to ping me on the PR as I'd like to see how this works. Cheers!
https://github.com/conda-forge/conda-forge-repodata-patches-feedstock/pull/791 is up, will remove draft if i win the CI lottery :slot_machine:
Checklist
conda-smithy
(Use the phrase code>@<space/conda-forge-admin, please rerender in a comment in this PR for automated rerendering)Fixing requirements, which were not properly updated for versions >=2.14.0, see the upstream changelog, specifically this pull request.
This PR should be backported for version 2.14.0.