Skip to content

bug(context): version in brief reflects root workspace package.json (0.10.0) not CLI package (0.16.0) #161

@stackbilt-admin

Description

@stackbilt-admin

Bug

charter context outputs:

- **Package**: charter v0.10.0

But the actual CLI version is 0.16.0 (charter --version confirms this). The brief is reading version from the root package.json (workspace root, which is at 0.10.0) rather than from packages/cli/package.json (the published CLI package at 0.16.0).

Reproduction

cd charter
charter context
# → Package: charter v0.10.0

charter --version
# → charter v0.16.0

Fix

When reading version for the brief, prefer the closest package.json that contains a matching name field (@stackbilt/cli) over the root package.json. Or, if charter knows its own version at compile time (via __VERSION__ constant), use that.

Impact

Low severity, but it creates confusion for agents and humans reading the brief — the version in the brief doesn't match what's installed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions