MNT: rerender

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-webservice.

I've rerendered the recipe as instructed in #187.

Here's a checklist to do before merging.

• [ ] Bump the build number if needed.

Fixes #187

[conda-forge-linter]

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.

[github-actions[bot]]

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you but ran into some issues. Please check the output logs of the latest rerendering GutHub actions workflow run for errors. You can also ping conda-forge/core for further assistance or try re-rendering locally.

This message was generated by GitHub actions workflow run https://github.com/conda-forge/conda-forge-ci-setup-feedstock/actions/runs/1872894709.

[beckermr]

@conda-forge-admin rerender

[isuruf]

@conda-forge-admin, rerender

[isuruf]

@conda-forge-admin, rerender

[beckermr]

I am closing this one. Will open a new PR with the changes above once smithy is fixed:

https://github.com/conda-forge/conda-smithy/issues/1593

[beckermr]

@kkraus14 @jakirkham any ideas why the cuda migrators are here? I think it'd be easier to put cuda in build and ignore the run exports maybe?

[isuruf]

yeah, add it to build and ignore_run_exports_from is better.