Skip to content

docs(adr): record v0.15.0 post-release verification #246

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mbeacom merged 1 commit into from
Sep 28, 2026
Merged

docs(adr): record v0.15.0 post-release verification #246

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 24 additions & 0 deletions docs/adr/0018-adopt-mcp-sdk-v2-and-serve-protocol-revision-2026-07-28-dual-era.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -490,3 +490,27 @@ as written; this amends it in two places.

A protocol-following 2025-era client that fails or sees a changed response still
falsifies this record, exactly as before.

## Post-release verification (2026-09-28, against published `@adrkit/mcp@0.15.0`)

The 2.1.0 verification above ran against a local build. This repeats it against
the artifact users install: `@adrkit/mcp@0.15.0` from npm, which resolves
`@modelcontextprotocol/server@2.1.0`, installed into a scratch directory and
launched as `node node_modules/@adrkit/mcp/dist/bin.js` with this repository as
its working directory. The official MCP Inspector 2.8.0 drove it headless in CLI
mode with `--protocol-era legacy` and `--protocol-era modern`.

| Call | Result, both eras |
|---|---|
| `tools/list` | the four tools; identical once keys are sorted |
| `search_decisions` (`query: bun`) | 17 items |
| `get_decision` (`ref: 0018`) | `found`, `accepted` |
| `get_decision_context` (`files: [packages/mcp/src/server.ts]`) | governing `0018` |
| `list_superseded` | 2 entries |

Every tool payload (`structuredContent` and `content`) was byte-identical
across the two eras. The one difference is the envelope the `2026-07-28` era
adds to each result, `_meta["io.modelcontextprotocol/serverInfo"]`, which named
`@adrkit/mcp` `0.15.0`. The counts match the pre-release run above.

Not exercised: the Inspector's web UI.
8 changes: 6 additions & 2 deletions ...ish-schema-v0-2-0-with-rfc-3339-seconds-retain-v0-1-0-and-validate-every-rec.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -172,8 +172,12 @@ pressure.
3. [x] Bump `SCHEMA_VERSION` to `0.2.0`, lift the `zod` cap and Dependabot
`ignore`, re-emit the schema, and re-pin `protected-surfaces.json`.
4. [x] Record the breaking change and the `:00` migration in the CHANGELOG.
5. [ ] Confirm, after the next site deploy, that
5. [x] Confirm, after the next site deploy, that
`https://adrkit.dev/schema/adr/v0.1.0/adr.schema.json` serves SHA-256
`1e1841151174cc5a8ed22dadae070f087477e5068bd928d5292c3acd2e2681cc` and
`https://adrkit.dev/schema/adr/v0.2.0/adr.schema.json` serves the canonical
file.
file. Observed 2026-09-28 after the v0.15.0 site deploy (`site.yml` push
run on `3440c60`, success): v0.1.0 returned HTTP 200 with SHA-256
`1e1841151174cc5a…` and `$id` `…/v0.1.0/adr.schema.json`; v0.2.0 returned
HTTP 200 with SHA-256 `1db3cafbfe082b24…`, equal to `schema/adr.schema.json`
on `main`, and `$id` `…/v0.2.0/adr.schema.json`.
Loading