ARM OSX Migrator

[regro-cf-autotick-bot]

This feedstock is being rebuilt as part of the ARM OSX migration.

Feel free to merge the PR if CI is all green, but please don't close it without reaching out the the ARM OSX team first at @conda-forge/help-osx-arm64.

If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase code>@<space/conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

_{This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/cf-scripts/actions/runs/6826296336, please use this URL for debugging.}

[conda-forge-webservices[bot]]

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.

[carterbox]

This will probably time out because of the clear disk space step?

EDIT: Or not because we already merged the patch to disable deleting the docker cache into conda-smithy.

[Tobias-Fischer]

We shouldn’t merge this - non-CUDA platforms are skipped, therefore there are no osx builds.

[jakirkham]

My guess is someone added PyTorch to the macOS ARM migrator and the bot is working its way through PyTorch's requirements

As this won't be used by PyTorch except on platforms using CUDA, this won't affect building PyTorch on macOS ARM

So closing is the right approach to let the bot know this package is "done" so it can move on to other PyTorch requirements (or PyTorch itself)