Actually publish v0.0.30

[shermansiu]

• Needed for vllm 0.9.2: Update version to 0.9.2 vllm-feedstock#10

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

NOTE: This should NOT be merged to main, but to a new branch instead. I don't think I can do that if I'm not a maintainer though.

Also, although CUDA architectures 9.0 and later can be built, they fail at test time due to the following error:

 │ Installing test environment
 │ ✔ Successfully updated the test environment
 │ Testing commands:
 │ Traceback (most recent call last):
 │   File "<frozen runpy>", line 198, in _run_module_as_main
 │   File "<frozen runpy>", line 88, in _run_code
 │   File "$PREFIX/lib/python3.12/site-packages/xformers/info.py", line 11, in <module>
 │     from . import __version__, _cpp_lib, _is_opensource, _is_triton_available, ops
 │   File "$PREFIX/lib/python3.12/site-packages/xformers/ops/__init__.py", line 9, in <module>
 │     from .fmha import (
 │   File "$PREFIX/lib/python3.12/site-packages/xformers/ops/fmha/__init__.py", line 10, in <module>
 │     from . import (
 │   File "$PREFIX/lib/python3.12/site-packages/xformers/ops/fmha/flash3.py", line 58, in <module>
 │     from ... import _C_flashattention3  # type: ignore[attr-defined]
 │     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 │ ImportError: dynamic module does not define module export function (PyInit__C_flashattention3)

[shermansiu]

@conda-forge-admin, please rerender

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

[h-vetinari]

We do not go back to old versions on main. I branched off an existing (never-published) commit where we were on 0.0.30 during the course of #50 - it might still be a good idea to keep the improvements since then (or not, I'll leave that up to you). I don't remember why we never published 0.0.30, probably because the feedstock had been stuck and 0.0.31 had been out already when we unblocked it

[shermansiu]

We do not go back to old versions on main. I branched off an existing (never-published) commit where we were on 0.0.30

Thanks for changing that! I agree, it might be a good idea to keep the improvements since then.

probably because the feedstock had been stuck and 0.0.31 had been out already when we unblocked it

Yeah, I think that's why

[shermansiu]

All checks have passed!