Repository navigation
Prepare core 0.12.0 and validator 0.13.1: user-friendly READMEs and validator defaults in core - #28
Merged
Conversation
Restructure the root, core, and validator READMEs around user tasks: package choice, quick starts, result handling, selector choice, browser use, troubleshooting, and compatibility. Replace experimental wording with "tested for MCP Description v0.8" and add mcpdesc compatibility badges. Use absolute links in package READMEs so they work on npmjs.com. Move development checks to CONTRIBUTING and the snapshot lifecycle to the validator maintainer guide. No API or behavior changes. Assisted by GitHub Copilot (agent mode).
Make the specification selector optional in core projection, merge, declaration selection, component resolution, and 0.8.0 migration. When omitted, operations use the validator default for the document's mcpdesc version (0.8.0-rev.20261021); explicit selectors still pin. Support the revision selector in core, pin @mcpdesc/validator 0.13.1, and document the upgrade from explicit '0.8.0' pins. Assisted by GitHub Copilot (agent mode).
Custom Tool-schema keywords alone validate under both 0.8.0 and the revision; the validity difference is x-mcp-header with protocol revisions other than 2026-07-28. Assisted by GitHub Copilot (agent mode).
Add selector as the canonical option across core operations, matching @mcpdesc/validator, with specification kept as a deprecated alias and conflicting values rejected with conflicting-selector-options. Deprecate the original 0.8.0 rules in core, matching the validator. Update locked dependencies to resolve npm audit advisories. Assisted by GitHub Copilot (agent mode).
ObjectIsAdvantag
left a comment
ObjectIsAdvantag
left a comment
Member
Author
There was a problem hiding this comment.
LGTM; latest release for mcpdesc v0.8, while work starts on v0.9
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.
Summary
Prepares two
latestreleases for the MCP Description 0.8-compatible packages. Release validator first, then core:@mcpdesc/validator@0.13.1: README rewrite only. No API, schema, or behavior changes.@mcpdesc/core@0.12.0: README rewrite; selectors become optional and follow the validator defaults; a canonicalselectoroption is added; the original0.8.0rules are deprecated. Core pins@mcpdesc/validator@0.13.1.0.9.0-draft.1support is not included and will follow on a dedicated branch as anextrelease.Documentation
mcpdesc: 0.8badge is added, matching mcptoolkit-contract.CONTRIBUTING.md, and the snapshot lifecycle goes todocs/validator-maintainer-guide.md.Core 0.12.0 changes
mcpdesc, currently0.8.0-rev.20261021. Merge resolves from its first document.sourcediagnostic, such asunsupported-format-version, with no fallback to older rules.selectoroption.selectoris now the canonical option name, matching the validator.specificationremains a deprecated alias, and conflicting values fail withconflicting-selector-options.0.8.0is deprecated, matching the validator. It still works when pinned and is listed indeprecatedCoreSpecifications.0.8.0-rev.20261021is supported by every selector-sensitive operation, and the exhaustive support matrix is updated.specification: '0.8.0'still get the original rules. Removing it adopts the issue Preserve unknown JSON Schema keywords and apply MCP-specific semantics only when defined #24 correction:x-mcp-headeris checked only for MCP2026-07-28. See "Upgrading from 0.11" in the core README.Security
npm audit fixupdates only the lockfile and resolves all reported advisories:vite,vitest,@vitest/mocker,source-map-js, andfast-uri(viaajv).npm auditnow reports 0 vulnerabilities. Package dependency ranges are unchanged, and the generated standalone validator bundle is byte-identical.Validation
npm run checkpasses: 63 core tests and 327 validator tests, plus declarations, browser and strict-CSP bundles, tarball contents, and an isolated consumer install of core 0.12.0 with validator 0.13.1.custom-tool-schema-keywords.json. It is valid under the default and invalid under the0.8.0pin, so the tests show that each operation follows the default when unpinned, honors explicit pins, accepts bothselectorand thespecificationalias, and rejects conflicting options.AI assistance disclosure
Prepared with GitHub Copilot (agent mode) under maintainer direction, including documentation, code, tests, and dependency updates. The maintainer reviews and is accountable for the result.