Skip to content

docs: Document xcodebuildmcp upgrade command#3

Open
cameroncooke wants to merge 1 commit intomainfrom
docs/upgrade-command
Open

docs: Document xcodebuildmcp upgrade command#3
cameroncooke wants to merge 1 commit intomainfrom
docs/upgrade-command

Conversation

@cameroncooke
Copy link
Copy Markdown
Collaborator

Adds documentation for the new xcodebuildmcp upgrade self-update
command landing in getsentry/XcodeBuildMCP#348.

What changes

  • app/docs/_content/cli.mdx: adds an upgrade row to the top-level
    commands table and a new "Keeping the CLI up to date" section covering
    the command, its --check and --yes flags, the npx caveat, and the
    non-interactive exit behavior.
  • app/docs/_content/installation.mdx: replaces the per-channel "Upgrade
    later" blocks with a single pointer to xcodebuildmcp upgrade, which
    already knows which package manager you installed with.
  • CLAUDE.md: records an "Audience and voice" rule directly under the
    Docs site section.

Why

The first draft leaned too far into implementation detail (which APIs
are called per channel, how release notes are fetched, truncation rules).
These docs are for end users of the CLI, not contributors working on the
XcodeBuildMCP implementation, so the revised pass covers only what the
user needs to decide and how to use the command. The CLAUDE.md rule
captures that guidance so future authors do not drift back to
implementation-heavy prose.

Note: the XcodeBuildMCP PR is not merged yet, so this depends on the
upgrade command actually shipping. Hold merging this until that lands.

Add a concise "Keeping the CLI up to date" section to the CLI page
covering the new `xcodebuildmcp upgrade` command, its `--check` and
`--yes` flags, the npx caveat, and the non-interactive exit behavior.
Update the Installation page to point at the self-update command instead
of repeating per-channel upgrade instructions.

Also record an Audience and voice rule in CLAUDE.md: docs are for end
users of XcodeBuildMCP, not contributors working on the implementation,
so drafts should focus on usage and user-impacting behavior rather than
internal mechanics (per-channel lookup strategies, fetch/parse details,
timeouts, etc.). The revised upgrade docs follow this rule.

Co-Authored-By: Claude <noreply@anthropic.com>
@vercel
Copy link
Copy Markdown
Contributor

vercel bot commented Apr 19, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
xcodebuildmcp-com Ready Ready Preview, Comment Apr 19, 2026 8:22pm

Request Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant