Skip to content

Reconcile version metadata (2.1.0) with the public release tag (v0.1.0) #4

Description

@JosephOIbrahim

The first public release is tagged v0.1.0, but in-repo version metadata reads 2.1.0 in three places: pyproject.toml, both *.uplugin (VersionName), and ue_mcp/__version__.py. So pip show ue-bridge reports 2.1.0 while the GitHub release is v0.1.0.

Do: pick the canonical scheme and align all sources — either bump the metadata to 0.1.0 to match the public release line, or adopt 2.1.0 for tags going forward. One source of truth ideally.


Filed as a post-v0.1.0 follow-up (out of v0.1.0 scope). 🤖 Claude Code

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions