Skip to content

Mesa 4 migration tracking #273

@wang-boyu

Description

@wang-boyu

Summary

This issue tracks the Mesa 4 migration effort for mesa-llm in one place and helps avoid partial, inconsistent migration changes from being merged through unrelated PRs.

Mesa 4 support is not complete yet. Until this tracking issue is resolved, the project should remain pinned to Mesa 3.x.

Status

Mesa 4 support is not an active merge target right now. Mesa 4 is still in alpha (v4.0.0a0), and Mesa's current stable version is still 3.x. Mesa 4 development tracking issue is: mesa/mesa#3132. We want to avoid merging partial or inconsistent Mesa 4 migration changes before the Mesa 4 API settles further.

Important

At this stage, mesa-llm is prioritizing maintenance work over Mesa 4 migration, with the near-term goal of closing existing maintenance bug tickets on Mesa 3.x.

Mesa 4 migration changes should be kept in dedicated Mesa 4 issues and PRs linked from this tracker.

If an otherwise unrelated PR includes Mesa 4 migration changes, those migration-related parts will not be reviewed as part of that PR and should be removed or split into a separate Mesa 4 PR linked here.

Related issues

Related PRs with Mesa 4 migration overlap

If I missed any related issues or PRs, please feel free to comment below and I’ll add them here.

Metadata

Metadata

Assignees

No one assigned

    Labels

    depedencyRelease notes label

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions