Skip to content

bug: requesthunt marketplace entry says version 1.0.0 but plugin.json says 2.0.0 #86

Description

@Kita-Toda

Split out of #85 at the maintainers' convenience — separate defect, same file.

The requesthunt entry in .claude-plugin/marketplace.json declares "version": "1.0.0", but skills/requesthunt/.claude-plugin/plugin.json declares "version": "2.0.0". It is the only skill in the marketplace where the two disagree; the other eight agree at 1.0.0.

Confirmed by claude plugin validate

$ claude plugin validate <marketplace-root>

⚠ plugins[0].version: Entry declares version "1.0.0" but
  skills/requesthunt/.claude-plugin/plugin.json says "2.0.0".
  At install time, plugin.json wins (calculatePluginVersion precedence) —
  the entry version is silently ignored. Update this entry to "2.0.0" to match.

Impact

Mostly cosmetic today, since plugin.json wins at install time — installs land in cache/opc-skills/requesthunt/2.0.0/, so users get v2 regardless. Two ways it can bite:

  1. The marketplace listing advertises 1.0.0 while installs resolve 2.0.0, so the browsing view disagrees with what users actually get.
  2. claude plugin tag validates that plugin.json and the enclosing marketplace entry agree, so a requesthunt--v2.0.0 release tag would fail this check until the entry is updated.

Suggested fix

Set the requesthunt entry in .claude-plugin/marketplace.json to "version": "2.0.0", matching plugin.json — the direction the validator recommends. Worth confirming 2.0.0 is the intended current version rather than plugin.json having been bumped prematurely.

Environment

  • marketplace at commit db8eff6
  • macOS 15 (Darwin 24.6.0)

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