claude-code - 💡(How to fix) Fix [BUG] Marketplace sync fails for all new marketplaces — "Some plugins in this marketplace have validation errors" [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#45130Fetched 2026-04-09 08:12:32
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
1
Participants
Timeline (top)
labeled ×4

Error Message

  • The error message gives no detail on which plugin or what the validation error is

Error Messages/Logs

Code Example

{
  "name": "my-marketplace",
  "owner": { "name": "My Org" },
  "metadata": { "description": "Test marketplace", "version": "1.0.0" },
  "plugins": [
    {
      "name": "my-plugin",
      "source": {
        "source": "git-subdir",
        "url": "owner/repo",
        "path": "plugins/my-plugin"
      },
      "description": "Test plugin.",
      "version": "1.0.0"
    }
  ]
}

---

{
  "name": "my-plugin",
  "version": "1.0.0",
  "description": "Test plugin."
}

---
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

Marketplace sync fails with "Some plugins in this marketplace have validation errors" for any new marketplace, including a brand-new repo with a single minimal plugin. Previously synced marketplaces continue to work.

What Should Happen?

Marketplace sync fails with "Some plugins in this marketplace have validation errors" for any new marketplace, including a brand-new repo with a single minimal plugin. Previously synced marketplaces continue to work.

Steps to reproduce

  1. Create a new private GitHub repo with the absolute minimum marketplace structure:

.claude-plugin/marketplace.json

{
  "name": "my-marketplace",
  "owner": { "name": "My Org" },
  "metadata": { "description": "Test marketplace", "version": "1.0.0" },
  "plugins": [
    {
      "name": "my-plugin",
      "source": {
        "source": "git-subdir",
        "url": "owner/repo",
        "path": "plugins/my-plugin"
      },
      "description": "Test plugin.",
      "version": "1.0.0"
    }
  ]
}

plugins/my-plugin/.claude-plugin/plugin.json

{
  "name": "my-plugin",
  "version": "1.0.0",
  "description": "Test plugin."
}
  1. Go to Claude Desktop → Cowork → Customize → Add marketplace
  2. Enter owner/repo or https://github.com/owner/repo
  3. Click Sync

Expected behavior

Marketplace syncs successfully and the plugin appears.

Actual behavior

Sync fails immediately with:

Marketplace sync failed Some plugins in this marketplace have validation errors.

Key observations

  • A marketplace that was synced before this issue started (delta-people-plugins) still works and can be re-synced successfully
  • A brand new repo created today with an identical structure (single plugin, minimal config) fails to sync
  • The marketplace.json and plugin.json are valid JSON and pass claude plugin validate locally
  • This affects multiple repos, not just one — tested with 4+ different repos
  • The error message gives no detail on which plugin or what the validation error is

Additional context

The working marketplace (delta-people-plugins) has the exact same structure: git-subdir source, minimal plugin.json with only name/version/description. The only difference is it was first synced before 2026-04-08.

Error Messages/Logs

Steps to Reproduce

Steps to reproduce Create a new private GitHub repo with the absolute minimum marketplace structure: .claude-plugin/marketplace.json

{ "name": "my-marketplace", "owner": { "name": "My Org" }, "metadata": { "description": "Test marketplace", "version": "1.0.0" }, "plugins": [ { "name": "my-plugin", "source": { "source": "git-subdir", "url": "owner/repo", "path": "plugins/my-plugin" }, "description": "Test plugin.", "version": "1.0.0" } ] } plugins/my-plugin/.claude-plugin/plugin.json

{ "name": "my-plugin", "version": "1.0.0", "description": "Test plugin." } Go to Claude Desktop → Cowork → Customize → Add marketplace Enter owner/repo or https://github.com/owner/repo Click Sync

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.1.72 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response

extent analysis

TL;DR

The issue can be mitigated by investigating the validation errors in the marketplace plugins, potentially by adding more detailed logging or error messages to identify the specific cause.

Guidance

  • Review the marketplace.json and plugin.json files for any potential issues or inconsistencies that could be causing the validation errors.
  • Consider adding more detailed logging or error messages to the Claude Code sync process to help identify the specific cause of the validation errors.
  • Test the sync process with a minimal marketplace configuration to isolate the issue and determine if it's related to a specific plugin or configuration.
  • Compare the configuration of the working marketplace (delta-people-plugins) with the new marketplaces to identify any potential differences that could be contributing to the issue.

Example

No specific code example is provided, as the issue is related to configuration and validation errors rather than code syntax.

Notes

The issue appears to be a regression, and the exact cause is unclear due to the lack of detailed error messages. Further investigation and logging are needed to identify the root cause.

Recommendation

Apply workaround: Investigate the validation errors and add more detailed logging or error messages to identify the specific cause, as the issue is likely related to a configuration or validation issue rather than a code problem.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING