Repository navigation
|
Question: What checks and release processes should Stellar DevKit implement before publishing stable releases of the SDK? I would like to understand the best approach to:
How would you structure a GitHub Actions pipeline that provides confidence in every release? |
Replies: 1 comment
|
I would structure the CI/CD pipeline into separate validation and release stages. 1. Pull request validation Every pull request should trigger:
2. Integration testing Use mocked RPC responses for deterministic tests and a dedicated testnet workflow for validating real network interactions. Test WASM parsing, contract inspection, simulation and transaction error handling. 3. Compatibility checks Define a supported Rust toolchain and dependency policy. Test the supported version matrix rather than relying on one development environment. 4. Security checks Include dependency vulnerability scanning, secret detection and appropriate static-analysis checks. 5. Release automation Require successful CI checks before release publication. Automate version tagging, changelog generation, build artifacts and release notes. 6. Release verification After publication, verify that the release artifacts are available, version metadata is correct and installation instructions work. My recommendation is to make pull-request validation mandatory, keep release publishing separate from ordinary CI, and use reproducible builds wherever practical. |
I would structure the CI/CD pipeline into separate validation and release stages.
1. Pull request validation
Every pull request should trigger:
2. Integration testing
Use mocked RPC responses for deterministic tests and a dedicated testnet workflow for validating real network interactions.
Test WASM parsing, contract inspection, simulation and transaction error handling.
3. Compatibility checks
Define a supported Rust toolchain and dependency policy. Test the supported version matrix rather than relying on one development environment.
4. Security …