[bot-automerge] xformers v0.0.31.post1

[regro-cf-autotick-bot]

It is very likely that the current package version for this feedstock is out of date.

Checklist before merging this PR:

• Dependencies have been updated if changed: see upstream
• Tests have passed
• Updated license if changed and license_file is packaged

Information about this PR:

1. Feel free to push to the bot's branch to update this PR if needed.
2. The bot will almost always only open one PR per version.
3. The bot will stop issuing PRs if more than 3 version bump PRs generated by the bot are open. If you don't want to package a particular version please close the PR.
4. If you want these PRs to be merged automatically, make an issue with @conda-forge-admin,please add bot automerge in the title and merge the resulting PR. This command will add our bot automerge feature to your feedstock.
5. 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 @conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

Pending Dependency Version Updates

Here is a list of all the pending dependency version updates for this repo. Please double check all dependencies before merging.

Name	Upstream Version	Current Version
pytorch-cpu	158733

_{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/16458574913 - please use this URL for debugging.}

[conda-forge-admin]

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/recipe.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipe/recipe.yaml:

• ℹ️ Jinja2 variable references are suggested to take a ${{<one space><variable name><one space>}} form. See lines [5].
• ℹ️ PyPI default URL is now pypi.org, and not pypi.io. You may want to update the default source url.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/16458673862. Examine the logs at this URL for more detail.}

[jeongseok-meta]

@conda-forge-admin, please rerun bot

[regro-cf-autotick-bot]

Due to the bot-rerun label I'm closing this PR. I will make another PR as appropriate. You should expect to wait at least a few hours, or possibly much longer, for a new PR.

_{This message was generated by https://github.com/regro/cf-scripts/actions/runs/16458973062 - please use this URL for debugging.}

[h-vetinari]

please rerun bot

@jeongseok-meta, please use this extremely sparingly. It wastes resources pointlessly, and it's generally much better to simply rebase the respective PR (the bot command is OK for people who are not comfortable doing that, or where there's horrific merge conflicts, but in any case, this concern does not apply on feedstocks where I'm a maintainer, because I know how to do it).

In this case in particularly, there isn't even anything to fix? The PR was legitimate and didn't have any merge conflicts. Beyond that, any changes here would still have been redundant, because I've already picked the respective commit into #52 locally, and I'm just waiting to see if the new architectures pass with CUDA 12.9 before I push it.

[jeongseok-meta]

@h-vetinari Good to know, thanks for the guidance!