Skip to content

Streaming / long-running pipelines do not automatically use the latest packages when requirements.txt is updated #6097

@Arthidon

Description

@Arthidon

Problem
Streaming / long-running pipelines do not automatically use the latest packages when requirements.txt is updated in the workspace (via Git sync or direct edit). This causes version drift.
Example

Mage Version:
OSS 0.9.77

Workspace: hub-orchestration (develop)
requirements.txt updated with hub_mage==0.11.0
Running streaming pipelines continue using old cached packages.

Desired Behavior
When a workspace’s requirements.txt changes, any streaming pipeline in that workspace should automatically install the updated dependencies on next run / restart.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions