[bot-automerge] xformers v0.0.32.post2

[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.

Closes: #57

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	159738

_{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/16993654960 - 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.

[conda-forge-admin]

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

• linter: passed
• azure: passed
• github-actions: passed

Thus the PR was passing and merged! Have a great day!

[shermansiu]

@conda-forge/xformers Will the build get triggered at some point? Or is there something we're waiting for?

[conda-forge-admin]

Hi! This is the friendly conda-forge automerge bot!

It appears that not all commits to this PR were made by the bot. Thus this PR is not being automatically merged. Please add the automerge label again (or ask a maintainer to do so) if you'd like to enable automerge again!

[h-vetinari]

Ah, I had forgotten why, but I had already seen this for 0.0.32:

xformers 0.0.32.post2 has requirement torch>=2.8, but you have torch 2.7.1.

We're waiting for conda-forge/pytorch-cpu-feedstock#409

[shermansiu]

Now that conda-forge/pytorch-cpu-feedstock#409 has been merged, I think it should be ready now!

[h-vetinari]

@beckermr, this looks like automerge should not have triggered here - there have been non-bot pushes into this PR and AFAICT no-one set the automerge label.

[h-vetinari]

this looks like automerge should not have triggered here - there have been non-bot pushes into this PR and AFAICT no-one set the automerge label.

Ping @beckermr @jaimergp , I feel mis-applied automerges warrant some attention, because that's potentially a security concern.

[shermansiu]

Potentially relevant logs:

• (Logs aren't that detailed, sadly) https://github.com/conda-forge/conda-forge-webservices/actions/runs/18247692344
• (No PR found for conda-forge/xformers-feedstock@c237d397b9bb4fdb2905012a28f30dbf5dc5e27c): https://github.com/conda-forge/conda-forge-webservices/actions/runs/18247701545
• (No PR found for conda-forge/xformers-feedstock@4d5ff07e0d004cb1679f0304f743ab2ce2604c67!?): https://github.com/conda-forge/conda-forge-webservices/actions/runs/18247701673
• (No PR found for conda-forge/xformers-feedstock@f8e83437d0be3e37f997553ef56a9fc4228712c6!?): https://github.com/conda-forge/conda-forge-webservices/actions/runs/18247701848

[shermansiu]

I don't have the time to thoroughly check, but maybe this is the issue?

From: https://github.com/conda-forge/conda-forge-webservices/blob/9f283a7b21ed04213ae8141bda5a752a695324a9/conda_forge_webservices/github_actions_integration/automerge.py#L384-L386

Relevant 3 lines plus surrounding context:

        # only if only ALLOWED_USERS have commits
        committers = {getattr(c.author, "login", None) for c in pr.get_commits()}
        if not all(c in ALLOWED_USERS for c in committers):
            _comment_on_pr_with_race(
                pr_for_admin,
                """\
Hi! This is the friendly conda-forge automerge bot!

It appears that not all commits to this PR were made by the bot. Thus this PR is \
not being automatically merged. Please add the `automerge` label again (or ask a \
maintainer to do so) if you'd like to enable automerge again!
""",
                "not all commits to this PR were made by the bot",
            )
            return False, "non-bot commits on a bot PR with the automerge slug"

        # can we automerge in this feedstock?
        if not _automerge_me(cfg):
            return False, "automated bot merges are turned off for this feedstock"

        return True, None

In this PR, there's one commit that regro-cf-autotick authored and h-vetinari committed, due to the rebase. We should probably check for both authors and committers? (i.e. That all authors AND committers are in ALLOWED_USERS)

Relevant PyGitHub documentation: https://github.com/PyGithub/PyGithub/blob/927cf227ab83b99d85d0cd0f491cd78ee9eea4b6/github/Commit.py#L122-L140