Skip to content

Recommend marketplace install; keep .mcp.json version in sync - #19

Open
christosgkoros wants to merge 3 commits into
mainfrom
docs/readme-marketplace-install-and-mcp-version
Open

Recommend marketplace install; keep .mcp.json version in sync#19
christosgkoros wants to merge 3 commits into
mainfrom
docs/readme-marketplace-install-and-mcp-version

Conversation

@christosgkoros

Copy link
Copy Markdown
Contributor

Summary

  • README: makes /plugin install postman@claude-plugins-official (and the claude plugin install postman@claude-plugins-official terminal variant) the primary install method. Moves the github: install and local-clone flow into collapsible "Alternative" sections. Re-applies the intent of the previously closed Update README: install via official plugin marketplace #15 on top of the current README.
  • .mcp.json: the X-Plugin-Version and User-Agent headers had drifted to 1.2.0 — bumped to match plugin.json.
  • Prevents future drift: release.yml now fails the release (on v* tags) if .mcp.json's version headers don't match plugin.json, mirroring the existing tag-vs-plugin.json check.
  • Docs: CLAUDE.md release process now instructs updating .mcp.json headers alongside plugin.json.
  • Version: bumped plugin.json to 1.3.1 (user-facing README change) with a matching CHANGELOG.md entry.

Test plan

  • release.yml is valid YAML; .mcp.json + plugin.json are valid JSON
  • Simulated the new sync check locally — passes (all three at 1.3.1)
  • Verify README renders correctly on GitHub (collapsible sections, code blocks)

Note

Version-sync is enforced at release/tag time (matching the existing tag check), not on every PR. Happy to add a pull_request-triggered validation job if you'd prefer it run earlier.

Generated with Claude Code

- README: make /plugin install postman@claude-plugins-official the primary
  install method; move GitHub and local-clone installs to collapsible alternatives
- .mcp.json: bump X-Plugin-Version and User-Agent to match plugin.json (were 1.2.0)
- release.yml: fail the release if .mcp.json version headers drift from plugin.json
- CLAUDE.md: document updating .mcp.json headers alongside plugin.json on release
- Bump plugin.json to 1.3.1 and add CHANGELOG entry

Co-Authored-By: Claude <noreply@anthropic.com>
christosgkoros and others added 2 commits August 2, 2026 18:07
Catch .mcp.json vs plugin.json version drift on every PR and push to main,
not just at release/tag time.

Co-Authored-By: Claude <noreply@anthropic.com>
Auto-requests review from the postman-api group members when a PR is ready
for review. Listed as individuals because the @postman-eng/postman-api team
is cross-org and cannot be referenced in a Postman-Devrel CODEOWNERS file.

Co-Authored-By: Claude <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant