nah is published in the community marketplace, but the entry is pinned to an old SHA even though its configured source ref has newer valid plugin builds.
Current community entry:
{
"name": "nah",
"source": {
"source": "git-subdir",
"url": "manuelschipper/nah",
"path": "plugins/nah",
"ref": "claude-marketplace",
"sha": "10caeba016a134c2c93231faf6f05ba2f380d646"
}
}That pinned SHA contains plugin version 0.7.1.
The configured source ref now points to:
- repo/ref:
manuelschipper/nah@claude-marketplace
- SHA:
3d2e24222a27c1145a2921b9b940d65182cc3feb
- plugin version:
0.8.3
I validated the current artifact locally:
git clone --depth 1 --branch claude-marketplace https://github.com/manuelschipper/nah
claude plugin validate nah/plugins/nah/.claude-plugin/plugin.json
Result: validation passed.
Possible cause: the public bump-plugin-shas action appears to resolve upstream with git ls-remote <repo> HEAD rather than using the marketplace entry's source.ref. For this repo, default branch HEAD is main, while the built Claude plugin artifact intentionally lives on claude-marketplace. main does not contain plugins/nah, so a HEAD-based refresh would miss or skip this entry even though the configured source.ref is valid.
Could the marketplace pin for nah be refreshed to 3d2e24222a27c1145a2921b9b940d65182cc3feb?
Also, can the SHA refresh pipeline resolve source.ref when present instead of default-branch HEAD? That would match the marketplace entry and avoid maintainers needing to change their repository default branch just for marketplace updates.
Related concern: I am avoiding resubmitting the plugin through the form because of the duplicate Published / oldest-version behavior reported in anthropics/claude-code#45051.
nahis published in the community marketplace, but the entry is pinned to an old SHA even though its configured source ref has newer valid plugin builds.Current community entry:
{ "name": "nah", "source": { "source": "git-subdir", "url": "manuelschipper/nah", "path": "plugins/nah", "ref": "claude-marketplace", "sha": "10caeba016a134c2c93231faf6f05ba2f380d646" } }That pinned SHA contains plugin version
0.7.1.The configured source ref now points to:
manuelschipper/nah@claude-marketplace3d2e24222a27c1145a2921b9b940d65182cc3feb0.8.3I validated the current artifact locally:
Result: validation passed.
Possible cause: the public
bump-plugin-shasaction appears to resolve upstream withgit ls-remote <repo> HEADrather than using the marketplace entry'ssource.ref. For this repo, default branchHEADismain, while the built Claude plugin artifact intentionally lives onclaude-marketplace.maindoes not containplugins/nah, so a HEAD-based refresh would miss or skip this entry even though the configuredsource.refis valid.Could the marketplace pin for
nahbe refreshed to3d2e24222a27c1145a2921b9b940d65182cc3feb?Also, can the SHA refresh pipeline resolve
source.refwhen present instead of default-branchHEAD? That would match the marketplace entry and avoid maintainers needing to change their repository default branch just for marketplace updates.Related concern: I am avoiding resubmitting the plugin through the form because of the duplicate Published / oldest-version behavior reported in anthropics/claude-code#45051.