Skip to content

Commit 115b097

Browse files
committed
release: 0.11.1 — listed on the official MCP Registry
One functional change, and it could not be made any other way. The registry proves you own the npm package by fetching it and matching a `mcpName` field against the server name. npm versions are immutable, so that field cannot be added to 0.11.0 — it needs a release of its own. Everything else here is the paperwork around it. `server.json` is the manifest, validated against the live registry rather than a schema file, which matters more than it sounds: the schema served at 2025-07-09 is stale and snake_case, the live one is 2025-12-11 and camelCase, and a local ajv run against the older copy happily reports "valid" for a document the registry rejects with a 422. That is the same shape as every bug that reached users this cycle — a green check standing in for a path nobody had run. Publishing happens from CI on release, over GitHub Actions OIDC. Partly because `mcp-publisher login github` is broken in every published build (modelcontextprotocol/registry#1543, fixed by #1588, unreleased as of v1.8.1), and partly because a listing published by hand drifts from the release the first time anyone forgets a step — which is precisely the failure this repo has now shipped three times. The workflow refuses to publish when server.json, the package version, the npm identifier or the release tag disagree. The drift guard grew two assertions: the manifest's version, npm entry, identifier, reverse-DNS name and 100-character description cap, and the mcpName/server-name coupling whose failure mode is a 400 and another immutable-version release. Both verified by injection rather than by being green. Also corrects the landing page, which claimed 429 tests against a suite of 433. It now says 430+, which stays true as tests are added. 434 tests. No API, protocol or tool changes — still 20 tools.
1 parent 3cb3f5d commit 115b097

7 files changed

Lines changed: 56 additions & 9 deletions

File tree

‎CHANGELOG.md‎

Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,36 @@
33
All notable changes to `tower-mcp`. Follows [Keep a Changelog](https://keepachangelog.com);
44
versions are [semver](https://semver.org) (0.x — expect movement).
55

6+
## 0.11.1 - 2026-09-30
7+
8+
**Listed on the official MCP Registry.** The registry is upstream of the directory
9+
ecosystem — Glama, PulseMCP and mcp.so sync from it — so one listing reaches further
10+
than filling in each of their forms by hand.
11+
12+
### Added
13+
14+
- `server.json` — the registry manifest, validated against the live registry rather
15+
than a schema file. (The schema served at `2025-07-09` is stale and snake_case; the
16+
current one is `2025-12-11` and camelCase, and validating locally against the old
17+
copy reports "valid" for a document the registry rejects with a 422.)
18+
- `mcpName` in the published package. The registry proves npm ownership by fetching the
19+
package and matching this field against the server name. **This is the only functional
20+
reason for this release** — npm versions are immutable, so the field cannot be added
21+
to one already published.
22+
- A workflow that publishes the manifest on every release, authenticating with GitHub
23+
Actions OIDC. `mcp-publisher login github` is broken in every published build
24+
(modelcontextprotocol/registry#1543, fixed by #1588 but unreleased as of v1.8.1);
25+
OIDC is a separate code path. Publishing from CI also means the listing cannot drift
26+
from the release, which hand-publishing does the first time anyone forgets a step.
27+
28+
### Fixed
29+
30+
- The landing page claimed 429 tests; the suite was at 433. Now states `430+`, which
31+
stays true as tests are added — a precise number that is wrong reads worse than an
32+
approximate one that is right.
33+
34+
No API, protocol or tool changes. Still 20 tools.
35+
636
## 0.11.0 - 2026-09-30
737

838
**A claim is only as fresh as the read that produced it.** Comparing write sets catches

‎README.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ agent → send_message (task) ─────────► agent claims
3636

3737
![Tower live board — a delegated task, a reply, and a prevented collision](docs/board.png)
3838

39-
> Status: **v0.11.0 — early, building in public.** Everything below works end-to-end today,
39+
> Status: **v0.11.1 — early, building in public.** Everything below works end-to-end today,
4040
> under an 80% coverage gate enforced in CI. What's shipped and what's next:
4141
> [CHANGELOG.md](./CHANGELOG.md) · design doc: [MVP-SPEC.md](./MVP-SPEC.md).
4242

‎package.json‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
{
22
"name": "tower-monorepo",
3-
"version": "0.11.0",
3+
"version": "0.11.1",
44
"private": true,
55
"description": "Tower \u2014 air-traffic control for AI agents editing a shared repo. Semantic pre-flight collision detection over MCP.",
66
"type": "module",

‎packages/cli/package.json‎

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
{
22
"name": "tower-mcp",
3-
"version": "0.11.0",
3+
"version": "0.11.1",
4+
"mcpName": "io.github.Rohanxmalik/tower",
45
"description": "Multiplayer for AI coding agents \u2014 delegate tasks across machines, see every claim, task and reply on one shared board, and catch collisions before the first keystroke. Over MCP, model-agnostic (Claude Code, Cursor, Codex).",
56
"type": "module",
67
"license": "MIT",

‎packages/shared/src/protocol.test.ts‎

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -249,8 +249,17 @@ describe("version and tool count cannot drift from what users are told", () => {
249249

250250
const npm = server.packages?.find((p) => p.registryType === "npm");
251251
expect(npm, "server.json declares no npm package").toBeDefined();
252-
const pkg = JSON.parse(read("packages/cli/package.json")) as { name: string };
252+
const pkg = JSON.parse(read("packages/cli/package.json")) as {
253+
name: string;
254+
mcpName?: string;
255+
};
253256
expect(npm?.identifier).toBe(pkg.name);
254257
expect(npm?.version).toBe(TOWER_VERSION);
258+
259+
// The registry proves npm ownership by fetching the *published* package and
260+
// matching its `mcpName` against the server name. If these two drift apart the
261+
// publish fails with a 400 — and because npm versions are immutable, the fix is a
262+
// whole new release, not an edit. That is what it cost the first time.
263+
expect(pkg.mcpName, "packages/cli/package.json is missing mcpName").toBe(server.name);
255264
});
256265
});

‎packages/shared/src/protocol.ts‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ import { z } from "zod";
99
/** One version string for the whole release: the MCP server, the remote client and
1010
* `/health` all report this, and the worker warns when major.minor drifts from the
1111
* server it talks to. Bump together with packages/cli/package.json. */
12-
export const TOWER_VERSION = "0.11.0";
12+
export const TOWER_VERSION = "0.11.1";
1313

1414
// ---------------------------------------------------------------------------
1515
// Core domain types

‎server.json‎

Lines changed: 11 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
"name": "io.github.Rohanxmalik/tower",
44
"title": "Tower",
55
"description": "Multiplayer for AI coding agents: collision detection before the edit, messaging, delegation.",
6-
"version": "0.11.0",
6+
"version": "0.11.1",
77
"websiteUrl": "https://rohanxmalik.github.io/Tower",
88
"repository": {
99
"url": "https://github.com/Rohanxmalik/Tower",
@@ -14,9 +14,16 @@
1414
{
1515
"registryType": "npm",
1616
"identifier": "tower-mcp",
17-
"version": "0.11.0",
18-
"transport": { "type": "stdio" },
19-
"packageArguments": [{ "type": "positional", "value": "serve" }]
17+
"version": "0.11.1",
18+
"transport": {
19+
"type": "stdio"
20+
},
21+
"packageArguments": [
22+
{
23+
"type": "positional",
24+
"value": "serve"
25+
}
26+
]
2027
}
2128
]
2229
}

0 commit comments

Comments
 (0)