Skip to content

[BUG] module_version in module.yaml stuck at 1.0.0 — should be 1.4.0 #53

@zarlor

Description

@zarlor

Description

skills/module.yaml and skills/bmad-bmb-setup/assets/module.yaml both declare module_version: 1.0.0, but the actual release is v1.4.0 (package.json, marketplace.json, and the git tag all say 1.4.0).

The BMAD installer reads the version from module.yaml, so every installation — including v1.4.0 — reports BMB as v1.0.0 in _bmad/config.yaml.

Files to fix

  • skills/module.yaml line 4: module_version: 1.0.0module_version: 1.4.0
  • skills/bmad-bmb-setup/assets/module.yaml line 4: module_version: 1.0.0module_version: 1.4.0

Steps to reproduce

  1. npx bmad-method@next install — select BMad Builder
  2. /bmad-bmb-setup to configure
  3. Check _bmad/config.yaml — BMB section shows version: 1.0.0
  4. Compare with ~/.bmad/cache/external-modules/bmb/package.json — shows 1.4.0

Expected behavior

module_version in module.yaml should match the release version (1.4.0). The version in _bmad/config.yaml after setup should reflect the actual installed version.

Actual behavior

module_version is 1.0.0 in both module.yaml files. It appears this field was never bumped after the initial 1.0.0 release — package.json and marketplace.json were updated for each release but module.yaml was missed.

Environment

  • BMad Method version: 6.2.3-next.12
  • bmad-builder: v1.4.0 (tag), main branch
  • Platform: Linux (WSL2), Claude Code CLI

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