Skip to content

update to 0.19.1#30

Merged
shermansiu merged 18 commits into
conda-forge:mainfrom
benmoss:0.19.1
Apr 27, 2026
Merged

update to 0.19.1#30
shermansiu merged 18 commits into
conda-forge:mainfrom
benmoss:0.19.1

Conversation

@benmoss
Copy link
Copy Markdown
Contributor

@benmoss benmoss commented Apr 20, 2026

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.

benmoss added 5 commits April 20, 2026 10:14
- Bump version to 0.19.1, build_number to 0
- Update pytorch_version to 2.10.0, torchvision to 0.25.0
- Update flash-attention vendored source to new commit
- Drop patches 0003/0004/0006 (gettid, CMAKE_ARGS, cpu.txt torch pin)
  upstreamed or no longer needed in 0.19.1
- Update patches 0002/0005 for changed context in 0.19.1
- Remove cutlass <4 host dep (vllm now uses cutlass 4.2.1 via FetchContent)
- Remove ray-cgraph, xformers, scipy, triton from run deps
- Add anthropic, ijson, mcp, opentelemetry-{api,sdk,exporter-otlp} to run deps
- Update many dep version constraints per requirements/common.txt
pytorch 2.10.0 requires libcusparse >=12.5.10.65, but the cuda 12.9
meta-package pins cuda-libraries 12.9.0.* which provides libcusparse
12.5.9.5.*. Removing the cuda meta-package lets the solver pick a
compatible libcusparse. The specific CUDA packages already listed in
host (cuda-cudart-dev, cuda-nvrtc-dev, etc.) are sufficient.
@conda-forge-admin
Copy link
Copy Markdown
Contributor

conda-forge-admin commented Apr 20, 2026

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipe/recipe.yaml) and found some lint.

Here's what I've got...

For recipe/recipe.yaml:

  • ❌ In conda-forge.yml: $.github_actions = {'self_hosted': True, 'timeout_minutes': 1200, 'triggers': ['push', 'pull_request']}.

    {'self_hosted': True, 'timeout_minutes': 1200, 'triggers': ['push', 'pull_request']} is not valid under any of the given schemas

    Schema
    {
      "anyOf": [
        {
          "$ref": "#/$defs/GithubActionsConfig"
        },
        {
          "type": "null"
        }
      ]
    }

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

benmoss added 6 commits April 20, 2026 14:07
The package is not in conda-forge and is only needed for the AWS
SageMaker entrypoint. vllm imports it at module load time via
api_server.py -> sagemaker/api_router.py, which breaks the build.
Add a no-op stub so the module imports cleanly; runtime SageMaker
functionality will still require the real package.
conda-forge ships libgomp as a separate package rather than bundling
it inside the torch wheel, so vllm's shim probe finds nothing and
find_library fails. Add a fallback to PREFIX/lib before the
find_library call.
@conda-forge-admin
Copy link
Copy Markdown
Contributor

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.

Comment thread recipe/conda_build_config.yaml Outdated
jaimergp and others added 3 commits April 23, 2026 12:24
MNT: Re-rendered with conda-smithy 3.61.1 and conda-forge-pinning 2026.04.21.11.53.26

Other tools:
- conda-build 26.3.0
- rattler-build 0.62.2
- rattler-build-conda-compat 1.4.13
ACL (Arm Compute Library) is downloaded from GitHub and built from
source during cmake configure. This fails on conda-forge because
oneDNN's FindACL.cmake cannot locate the built artifacts. Add a
VLLM_SKIP_ACL env var guard around the entire ACL section and set
it for aarch64 builds. oneDNN still works without ACL, just without
the ACL-accelerated kernels.
@benmoss benmoss marked this pull request as ready for review April 24, 2026 13:01
@benmoss
Copy link
Copy Markdown
Contributor Author

benmoss commented Apr 24, 2026

Not sure if renumbering the patches is high priority or not :)

@shermansiu
Copy link
Copy Markdown
Contributor

And 0.20.0 is also out, wow

Comment thread recipe/recipe.yaml
- aarch64 and use_cuda # Still have issues locating CUDA for the aarch64 build
# - not use_cuda # Just build CUDA for now
# - match(python, "!=3.10") # Until all the builds succeed
# See XXX on why we need this skip to distinguish runners for GPU builds vs CPU builds
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we please fill in the actual link here?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wait, that's from jaimergp's commit...

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah.... it's supposed to be a reference to conda-forge/conda-forge-pinning-feedstock#6910

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! I suppose we can update it for the 0.20.0 build!

@shermansiu shermansiu merged commit 9e256e0 into conda-forge:main Apr 27, 2026
17 checks passed
@shermansiu
Copy link
Copy Markdown
Contributor

Thanks so much, @benmoss! 😄

@benmoss benmoss deleted the 0.19.1 branch April 27, 2026 14:11
Comment thread recipe/recipe.yaml
script:
# Pick an arbitrary test to run: some of the other ones rely on a bunch of external packages
- pytest ./tests/core/test_scheduler.py
- pytest ./tests/config/test_config_utils.py
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is a test for non-core functionality. Why was this changed?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Probably because the tests/core directory was removed in 0.19.1, so he picked another random test.

https://github.com/vllm-project/vllm/tree/v0.19.1/tests/

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants