Skip to content

fix(ci): harden soroban deploy workflow against transient failures#922

Open
MarvyNwaokobia wants to merge 2 commits into
HyperSafeD:mainfrom
MarvyNwaokobia:fix/soroban-deploy-ci
Open

fix(ci): harden soroban deploy workflow against transient failures#922
MarvyNwaokobia wants to merge 2 commits into
HyperSafeD:mainfrom
MarvyNwaokobia:fix/soroban-deploy-ci

Conversation

@MarvyNwaokobia

Copy link
Copy Markdown

Summary

  • Add retry loop (3 attempts, 10s backoff) for Soroban CLI install — replaces || true which silently swallowed failures while soroban --version still exited 127 on transient SSL errors
  • Skip deploy on schedule triggers — the 6-hour cron should only build & validate the WASM, not attempt deployment without secrets
  • Handle missing artifacts gracefullyif-no-files-found: ignore on uploads, continue-on-error on downloads, gate validation steps on download success

Context

The scheduled workflow has been failing on every 6-hour cron run (3+ failures on 2026-06-20 alone). The most recent failure was a transient SSL error downloading the csv crate during cargo install soroban-cli, which cascaded into a full job failure.

Test plan

  • Verify workflow YAML is valid (no syntax errors)
  • Confirm scheduled runs pass (build-only, no deploy attempt)
  • Confirm push-triggered runs still deploy normally
  • Confirm workflow_dispatch dry-run still works

🤖 Generated with Claude Code

Marvy and others added 2 commits April 25, 2026 19:02
…rSafeD#548)

- Add scripts/verify-csp-compliance.js: byte-level audit of generated
  JS glue code to detect eval() and new Function() CSP violations
- Require wasm-bindgen >=0.2.84 for CSP-friendly code generation
- Add mandatory 'Verify CSP Compliance' step in CI after WASM build
- Add frontend/tests/e2e/csp-security.spec.ts: Playwright E2E test that
  loads WASM module under a strict CSP (no unsafe-eval) header
- Create docs/wasm-security-hardening.md with deployment guidance
- Update DOCUMENTATION_INDEX.md with links to new security docs

Closes HyperSafeD#548
The scheduled cron was failing every 6 hours due to:
- Soroban CLI install failing on transient SSL errors (|| true swallowed
  the failure but soroban --version still exited 127)
- Schedule trigger attempting deployment without secrets
- Missing artifact uploads crashing downstream jobs

Add install retry loop, skip deploy on schedule runs, and handle missing
artifacts gracefully.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@vercel

vercel Bot commented Jun 20, 2026

Copy link
Copy Markdown

@MarvyNwaokobia is attempting to deploy a commit to the gbangbolaoluwagbemiga's projects Team on Vercel.

A member of the Team first needs to authorize it.

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.

1 participant