Repository navigation
docs(adr): record v0.15.0 post-release verification - #246
Merged
Merged
Conversation
- ADR-0043 action item 5: after the v0.15.0 site deploy, v0.1.0 serves SHA-256 1e184115... and v0.2.0 serves 1db3cafb..., equal to main's schema/adr.schema.json, each at its own $id. - ADR-0018: appended a post-release section. The published @adrkit/mcp@0.15.0 (server SDK 2.1.0), driven headless by Inspector 2.8.0 on both eras, returned identical tool payloads for all four tools; the only difference is the 2026-07-28 serverInfo _meta envelope, naming 0.15.0. Counts match the pre-release run. Signed-off-by: Mark Beacom <m@beacom.dev>
Decisions governing this change
|
There was a problem hiding this comment.
Copilot review overview
🟢 Approval recommended
Documentation-only verification changes have no unresolved review issues.
Review effort: Lite
Findings: None
What changed in this PR
Records v0.15.0 post-release verification for schema hosting and the published MCP package.
Changes:
- Marks ADR-0043 schema deployment verification complete.
- Appends published MCP dual-era verification results to ADR-0018.
- No executable code or ratified decision text changed.
| File | Description |
|---|---|
docs/adr/0043-publish-schema-v0-2-0-with-rfc-3339-seconds-retain-v0-1-0-and-validate-every-rec.md |
Records deployed schema hashes and $id checks. |
docs/adr/0018-adopt-mcp-sdk-v2-and-serve-protocol-revision-2026-07-28-dual-era.md |
Records published MCP verification across both protocol eras. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What and why
Records the post-release checks for v0.15.0. Docs only: two ADRs, with only an action item ticked and a section appended. No ratified text changes.
/schema/adr/v0.1.0/adr.schema.jsonreturns HTTP 200 with SHA-2561e184115…, byte-identical to the original v0.1.0 publication./schema/adr/v0.2.0/adr.schema.jsonreturns1db3cafb…, the same asschema/adr.schema.jsononmain. Each is served at its own$id.@adrkit/mcp@0.15.0from npm (server SDK 2.1.0), driven headless by Inspector 2.8.0 with--protocol-era legacyandmodern. All four tools returned byte-identical payloads on both eras. The only difference is the2026-07-28serverInfo_metaenvelope, which names0.15.0. The counts match the pre-release run: 17 search results, 0018 found, 0018 governingserver.ts, and 2 superseded entries. The Inspector web UI was not exercised.Other release checks, not recorded in an ADR:
@adrkit/{cli,core,evaluator,mcp}at0.15.0.v0.15.0is an annotated tag on3440c60, and the remotev0points at the same commit.ghcr.io/mbeacom/adrkitv0.15.0,v0andlatestall resolve to one amd64 + arm64 index.dev.adrkit/mcp0.15.0as latest.ADR-0043 is still
proposed. Ratifying it is the maintainer's call and isn't part of this PR.Checklist
adr lintpasses (43 records),check:stale-refspasses, andemit:manifestproduces no diff.