Stamp manifest_fingerprint from the packed files at publish - #38
Merged
Merged
Conversation
Plan v3 §2/§5.4 leftover. The peer heartbeats manifest_fingerprint and signature, but both shipped empty. The publish workflow now stamps the fingerprint (sha256 over the packed file set, after build) and signs it when ORGX_MANIFEST_SIGNING_KEY is set, matching the server's verifyManifest. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
hopeatina
added a commit
that referenced
this pull request
Sep 25, 2026
…est fingerprint (#39) Ships #37 (pin the OpenCode work capture mode explicitly) and #38 (stamp manifest_fingerprint from the packed files at publish). Versions aligned across package.json, package-lock.json and plugin.manifest.json; the peer test's gateway_version fixture follows the version. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
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.
Plan v3 leftover (release identity). The peer heartbeats
manifest_fingerprintandsignature, but both shipped empty. The publish workflow now stamps the fingerprint (sha256 over the packed file set, computed after build) and signs it withORGX_MANIFEST_SIGNING_KEYwhen that secret exists, matching the server'sverifyManifest. Same script as useorgx/orgx-codex-plugin#60.Checks: 3 stamp tests; full test suite; a local run stamps
sha256:1a20fe…over the built package.🤖 Generated with Claude Code