Repository navigation
fix: address #270, #271, #273, #274 - #379
Merged
veracindarella merged 4 commits intoOct 23, 2026
Merged
Conversation
…eplace placeholde Closes veracindarella#270
…to release workfl Closes veracindarella#271
…mal production im Closes veracindarella#274
|
@Atisan12 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
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
fix: address #270, #271, #273, #274
What was solved
#270 — SEC-32: Add security contact verification — replace placeholder email
Replace the placeholder security contact email in SECURITY.md with a real monitored address, align the README Security section, and audit docs/ files for placeholder emails. The issue is documentation-only; no code changes are needed.
Addressed:
#271 — OPS-16: Add mainnet deployment dry-run check to release workflow
Add a mainnet-dry-run job to the release workflow that runs after the release job on tag push, invoking
stellar contract deploy --dry-runagainst the mainnet RPC and failing on non-zero exit; ensure the real mainnet deploy is a separate manual workflow_dispatch, and document mainnet deployment steps in docs/operations-runbook.md.Addressed:
mainnet-dry-runthat runs after thereleasejob on tag pushstellar contract deploy --dry-runagainst the mainnet RPC in the dry-run job#273 — OPS-18: Add contract ABI/interface diff check to CI
Add a CI-enforced contract interface diff check for the stream contract: a script that generates a JSON interface spec from the compiled WASM via
stellar contract bindings, a committed baseline atcontracts/stream/interface.json, a CI workflow step that regenerates and diffs against the baseline with a clear failure diff, and CONTRIBUTING.md documentation for intentionally updating the interface file.Addressed:
stellar contract bindingscontracts/stream/interface.json.github/workflows/ci.yml) that regenerates the spec and diffs it against the committedcontracts/stream/interface.json#274 — OPS-19: Add Docker multi-stage build for minimal production image
Add a multi-stage Dockerfile (builder compiles WASM, minimal runtime holds only artifacts), wire docker-compose build service to it, publish the image to GHCR on tag push in CI, and document the Docker workflow in the README.
Addressed:
builderstage compiles the WASM contract,runtimestage contains only WASM artifactsbuildservice to use the multi-stage imageChanges
SECURITY.md(modify).github/workflows/release.yml(modify).github/workflows/ci.yml(modify)README.md(modify)docs/operations-runbook.md(modify)contracts/stream/interface.json(create)scripts/check-interface.sh(create)docker-compose.yml(modify)Dockerfile(modify)Approach
Issues
Closes #270
Closes #271
Closes #273
Closes #274