Skip to content

auto-deploy-contracts-to-testnet#209

Merged
phertyameen merged 4 commits into
bridgelet-org:mainfrom
MaryammAli:auto-deploy-contracts-to-testnet
Jun 28, 2026
Merged

auto-deploy-contracts-to-testnet#209
phertyameen merged 4 commits into
bridgelet-org:mainfrom
MaryammAli:auto-deploy-contracts-to-testnet

Conversation

@MaryammAli

Copy link
Copy Markdown
Contributor

PR Title

ci: automate Soroban contract deployment to Stellar Testnet on merge to main

Summary

This PR introduces an automated GitHub Actions deployment pipeline that deploys all Soroban contracts to the Stellar Testnet whenever changes are merged into the main branch. Deployments only occur after all tests and integration checks pass, ensuring only validated contract code reaches the testnet.

The workflow securely uses GitHub Secrets for deployment credentials, publishes deployed contract IDs as workflow artifacts, and includes a deployment summary for easy reference.

Changes Made

CI/CD Workflow

  • Added GitHub Actions workflow to automatically deploy contracts after successful merges to main.

  • Configured deployment to run only after:

    • Rust unit tests pass (cargo test)
    • Local Stellar sandbox integration tests complete successfully
  • Prevents deployment if any validation step fails.

Automated Testnet Deployment

  • Deploys all Soroban contracts to the Stellar Testnet.
  • Uses the configured deployer account stored securely as a GitHub Secret.
  • Eliminates manual deployment steps after successful merges.

Deployment Artifacts

  • Saves deployed contract IDs as GitHub Actions artifacts.

  • Generates a workflow summary containing:

    • Contract names
    • Testnet contract IDs
    • Deployment status
    • Deployment timestamp

Security

  • Deployment credentials are loaded from GitHub Secrets.
  • No private keys or sensitive credentials are stored in the repository or workflow logs.

Documentation

  • Updated deployment documentation with:

    • CI deployment flow
    • Required GitHub Secrets
    • Deployment prerequisites
    • How to retrieve deployed contract IDs from workflow artifacts

Files Modified

  • .github/workflows/testnet-deploy.yml
  • Deployment scripts (if applicable)
  • docs/ deployment documentation
  • Related CI configuration files

Acceptance Criteria

auto-deploy-contracts-to-testnet
@drips-wave

drips-wave Bot commented Jun 26, 2026

Copy link
Copy Markdown

@MaryammAli 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! 🚀

Learn more about application limits

@phertyameen

Copy link
Copy Markdown
Contributor

@MaryammAli fix faining CI please

@phertyameen

Copy link
Copy Markdown
Contributor

@MaryammAli What is the update on this fix?

fixes
@MaryammAli

Copy link
Copy Markdown
Contributor Author

kindly approve workflow
@phertyameen

@phertyameen

Copy link
Copy Markdown
Contributor

@MaryammAli Also resolve conflict

@MaryammAli

Copy link
Copy Markdown
Contributor Author

@phertyameen
approve workflow

@phertyameen phertyameen left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great work. Please feel free to apply for more issues here in the future

@phertyameen phertyameen merged commit 110bc1d into bridgelet-org:main Jun 28, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

CI: auto-deploy contracts to testnet on merge to main Improve scripts/build.sh: add checksums and artefact output

2 participants