build: offline verification, samples, and MCP gateway records#837
Merged
Conversation
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
Release preparation for v0.15.1: offline verification, generated samples, and MCP gateway records. Bumps all workspace package versions 0.15.0 -> 0.15.1 plus the version-bearing metadata and generated artifacts; adds the CHANGELOG entry. No wire, schema, signing, or registry changes; the public API change in this release line is additive (
peac verify --public-key, merged in #833).Scope
pnpm version:bump 0.15.1(65 packages; publish manifest; MCP server.json/manifest.json; spec and conformance version fields; build-registry constant).SERVER_VERSION,smithery.yamlpin,docs/releases/facts.jsonversion and test metrics, package-surface-audit allowlist, telemetry version constant, regenerated kernel error tables and conformance matrix.release_date,dist_tag) intentionally remain at pre-release values; they are stamped post-tag per docs/RELEASING.md.Validation
verify-release: 0 failed (build_targets matches turbo dry-run: 105).--strict, version sync: all pass.peac --versionreports 0.15.1;samples generate->verify --public-keyverifies offline; example demos pass.