mirror of
https://github.com/callstack/agent-device.git
synced 2026-09-14 20:06:34 +08:00
Claude
e8a9abdd8d
Registry scanners diff the repository's tool surface per version string, so a
released number left on main while main keeps changing is indistinguishable
from a republished ("rug-pull") version — two scans of the same version see
two different tool sets (AS-012).
- release:publish now runs release:mark-dev after npm publish, moving
package.json and the synchronized server.json to the next patch with a
-dev prerelease marker.
- release:prepare refuses to publish while the -dev marker is in place, so
a forgotten version bump cannot ship a prerelease as latest.
- Mark the current tree 0.20.11-dev: main had been sitting on the published
0.20.10 while the tool surface kept changing, which is the live finding.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wb8EuoySL26UsdtCtRj5X8
22 lines
602 B
JSON
22 lines
602 B
JSON
{
|
|
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
|
|
"name": "io.github.callstack/agent-device",
|
|
"title": "agent-device",
|
|
"description": "MCP server for mobile app automation: verify, control, and debug iOS, Android, TV, and desktop apps",
|
|
"repository": {
|
|
"url": "https://github.com/callstack/agent-device",
|
|
"source": "github"
|
|
},
|
|
"version": "0.20.11-dev",
|
|
"packages": [
|
|
{
|
|
"registryType": "npm",
|
|
"identifier": "agent-device",
|
|
"version": "0.20.11-dev",
|
|
"transport": {
|
|
"type": "stdio"
|
|
}
|
|
}
|
|
]
|
|
}
|