From 5b104ef36e54be525434d94310f9b3e788c4c67a Mon Sep 17 00:00:00 2001 From: Jo D Date: Thu, 30 Apr 2026 14:46:38 -0400 Subject: [PATCH] ci: rebuild inside cloned repo for devnet verify solana-verify verify-from-repo always re-clones the repo into a fresh temp directory; with --skip-build it expects the .so to already exist in that clone, which it never does (build-verified writes target/ in the workflow workspace, not the clone). The result was: Skipping local build and writing verify data on chain Uploading the program verification params to the Solana blockchain... Error: No such file or directory (os error 2) Set skip-build: 'false' so solana-verify performs its own Docker build inside the cloned repo before uploading the verification PDA. Adds a few minutes to the devnet release but makes the step actually work. --- .github/workflows/release.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index e96a003..eeac2e4 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -118,7 +118,7 @@ jobs: network: devnet mount-path: program commit-hash: ${{ github.sha }} - skip-build: 'true' + skip-build: 'false' # ============================================ # mainnet: bundle into Squads multisig proposal