feat(release): gen:integrity — signed release-integrity manifest - #27
Closed
BlackChar92 wants to merge 1 commit into
Closed
feat(release): gen:integrity — signed release-integrity manifest#27BlackChar92 wants to merge 1 commit into
BlackChar92 wants to merge 1 commit into
Conversation
…rator Generates integrity.json pinning the npm tarball (sha512/shasum via reproducible npm pack) and the agent-facing raw files (mcp-api-list.md, README, CHANGELOG, LICENSE, package.json — sha256) to a git commit anchor, with the tool-surface counts cross-parsed from the generated catalog. Deterministic on an unchanged tree (no wall clock — commit date only), so a CI freshness check can enforce it like gen:api-list. The manifest itself is gitignored: it's a release artifact (generate per release, GPG detach-sign, attach to the GitHub Release), not a committed file — committing it would chase its own commit hash. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Contributor
Author
|
Withdrawing: release-integrity signing should come from the org's own key / official release pipeline (npm --provenance) rather than a contributor key — keeping this as a local tool for now. The freshness gate in #26 stands on its own. |
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
1 participant
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.
Adds
npm run gen:integrity→integrity.json: a release-integrity manifest pinning the npm tarball (reproduciblenpm packsha512/shasum) and the agent-facing raw files (mcp-api-list.md, README, CHANGELOG, LICENSE, package.json — sha256) to a git commit anchor, with tool-surface counts (98 / 58 read / 40 write / 27 destructive) cross-parsed from the generated catalog.Design notes:
gen:api-list.integrity.json(+.asc) are gitignored — a manifest that contained its own commit's hash would chase itself. Generate per release, GPG detach-sign, attach to the GitHub Release.gpg --verifyGood signature ✅.Companion to #26 (catalog freshness gate); together they make the published tool surface tamper-evident.
🤖 Generated with Claude Code