makeplane / makeplane/plane

[bug]: plane --version reports 0.1.0 when plane-compose 0.2.0 is installed

Open Beginner friendly
#9,002 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
59.6k
Forks
5.8k
Avg merge
1d 22h
Merged PRs (30d)
49

Description

Context for this and four related tickets: https://github.com/orgs/makeplane/discussions/8999

I have searched existing issues; no existing report covers this. Filing via API rather than the issue form, so the form fields (Environment, Browser, Variant, Version) are inlined below.

  • Environment: Production
  • Browser: Other (CLI tool)
  • Variant: Cloud (tested against api.plane.so)
  • Version: plane-compose 0.2.0 (per pipx list and per https://pypi.org/project/plane-compose/, which lists 0.2.0 as the latest release)
Current behavior

pipx install plane-compose confirms it has installed plane-compose 0.2.0. However, running plane --version self-reports plane version 0.1.0.

What I expect: the version string in plane --version matches the installed package version. As-is, the discrepancy makes it harder to write accurate bug reports against upstream -- users have to reason about whether 0.1.0 is a stale string or whether they have an older install. (See #9000 and #9001, where I had to footnote this discrepancy each time to avoid confusing reviewers about which version exhibited the behavior.)

The fix is presumably to pin the CLI's version string to the package version at build time -- e.g., reading from importlib.metadata rather than a hardcoded constant.

Steps to reproduce
  1. pipx install plane-compose. Pip's installation summary confirms installed package plane-compose 0.2.0:
    $ pipx install plane-compose
    ...
    installed package plane-compose 0.2.0, installed using Python 3.14.4
      These apps are now available
        - plane
    
  2. pipx list | grep plane-compose confirms package plane-compose 0.2.0.
  3. plane --version outputs plane version 0.1.0:
    $ plane --version
    plane version 0.1.0
    
  4. Compare: installed package is 0.2.0; CLI self-reports 0.1.0.

Lowest priority of the five tickets in this batch -- filed for completeness rather than urgency.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the plane-compose CLI entry point and search the package for the hardcoded 0.1.0 version string, then check how the package metadata is exposed. Install with pipx and compare pipx list with plane --version; done means the CLI reports the installed package version, 0.2.0 in the reproduction.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cli
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
72/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.