Skip to content

Dependency conflict: KServe uvicorn[standard] version range incompatible with Feast 0.50.0 #4646

Closed as not planned

Description

@aniketpalu

/kind bug

What steps did you take and what happened:
When trying to install Feast (v0.50.0) alongside KServe (v0.15.2) in the same Python environment, the installation fails due to incompatible uvicorn[standard] version requirements between the two packages.

  • Feast v0.50.0 requires uvicorn[standard]==0.34.0 (pinned to a specific version)
  • KServe v0.15.2 requires uvicorn[standard]>=0.30.6,<0.31.0 (restricted version range)

These requirements are mutually exclusive, leading to dependency resolution errors.
This blocks workflows in environments (e.g., RHOAI) that require both Feast and KServe together.

What did you expect to happen:
Feast and KServe should be installable together without dependency conflicts, allowing both packages to function correctly in the same Python environment.

What's the InferenceService yaml:
N/A — This issue is related to Python package dependencies and not a specific InferenceService manifest.

Anything else you would like to add:
Root Cause:

  • Feast pins uvicorn[standard]==0.34.0
  • KServe restricts to >=0.30.6,<0.31.0
  • This version mismatch prevents co-installation

Impact:

  • Users cannot install Feast and KServe in the same environment
  • Blocks development/deployment workflows that require both packages

Proposed Solution:
Update KServe’s uvicorn[standard] version range to be compatible with newer uvicorn versions.

Error Details:
uv sync× No solution found when resolving dependencies for split (python_full_version == '3.12.'):
╰─▶ Because feast==0.50.0 depends on uvicorn[standard]==0.34.0
and kserve==0.15.2 depends on uvicorn[standard]>=0.30.6,<0.31.0,
we can conclude that kserve==0.15.2 and feast[spark]==0.50.0 are incompatible.
And because your project depends on feast[spark]==0.50.0 and kserve==0.15.2,
we can conclude that your project's requirements are unsatisfiable.

Environment:

  • KServe Version: 0.15.2

Activity

  1. github-actions commented on May 4, 2026

    @github-actions

    This issue has been automatically detected as stale because it has not had any activity for 30 days. It will receive two more warnings before being automatically closed. If this issue is still relevant, please comment or remove the stale label. Add the ignore-stale label to keep this issue open indefinitely. Warning 1 of 3.

  2. self-assigned this
    on May 4, 2026
  3. github-actions commented on Jun 4, 2026

    @github-actions

    This issue has been automatically detected as stale because it has not had any activity for 30 days. It will receive two more warnings before being automatically closed. If this issue is still relevant, please comment or remove the stale label. Add the ignore-stale label to keep this issue open indefinitely. Warning 1 of 3.

  4. github-actions commented on Jun 6, 2026

    @github-actions

    This issue is still stale. It will receive one more warning before being automatically closed. Please comment or remove the stale labels if this issue is still relevant. Add the ignore-stale label to keep this issue open indefinitely. Warning 2 of 3.

  5. github-actions commented on Jun 23, 2026

    @github-actions

    This is the final warning. This issue will be automatically closed if there is no activity within the next day. Please comment or remove the stale labels if this issue is still relevant. Add the ignore-stale label to keep this issue open indefinitely. Warning 3 of 3.

  6. github-actions commented on Jul 15, 2026

    @github-actions

    This issue has been automatically closed after 3 warnings with no activity. If you believe this issue is still relevant, feel free to reopen it.

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

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions