feat(deploy): add contract deployment artifact manifest generator (#716) - #736
Open
ravendevhub wants to merge 1 commit into
Open
feat(deploy): add contract deployment artifact manifest generator (#716)#736ravendevhub wants to merge 1 commit into
ravendevhub wants to merge 1 commit into
Conversation
…re-Foundry#716) - Generate structured JSON deployment manifest recording contract ID, network, RPC, timestamp, and git commit - Exclude all private keys and secrets with validation guards - Provide schema documentation in docs/CONTRACT_DEPLOYMENT_MANIFEST.md and example in deployments/
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.
Summary
Resolves #716 by introducing a structured deployment manifest generator (
scripts/generate-deployment-manifest.js) that records contract identifiers, network parameters, RPC endpoints, and git commits while strictly validating that no private keys or secrets are written to output files.Changes
scripts/generate-deployment-manifest.js):contract_id,wasm_hash,network,rpc_url,passphrase,deployer_public_key,timestamp, andgit_commit.S...) are detected.deployments/deployment-manifest.example.json.docs/CONTRACT_DEPLOYMENT_MANIFEST.md.Acceptance Criteria