ci: pass keypair content (not path) to devnet release actions#71
Merged
ci: pass keypair content (not path) to devnet release actions#71
Conversation
solana-developers/github-actions/{write-program-buffer,program-upgrade,
metadata-upload,verify-build} all expect the `keypair` input to be the
keypair file *content* (a JSON array string), then internally write it to
./deploy-keypair.json. We were passing the path /tmp/deployer.json, so
the action wrote the literal string "/tmp/deployer.json" into the file
and the solana CLI rejected it with "Input must be a JSON array".
Pass ${{ env.DEPLOYER_KEYPAIR }} (Doppler-injected) directly for the
devnet path. Mainnet/Squads steps left unchanged for now and still rely
on the materialize step; they can be migrated when next exercised.
Compute Unit Report
Generated: 2026-04-30 |
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
Write program bufferfailing in the release workflow withInput must be a JSON array.${{ env.DEPLOYER_KEYPAIR }}(Doppler-injected content) to the devnet sub-actions instead of the file path/tmp/deployer.json.Root Cause
The
solana-developers/github-actions/{write-program-buffer, program-upgrade, metadata-upload, verify-build}actions all internally do:i.e. they treat
inputs.keypairas the keypair content, not a file path. We were passing/tmp/deployer.json, so the action wrote the literal string/tmp/deployer.jsoninto./deploy-keypair.jsonandsolana program write-bufferrejected it.Scope
Materialize deployer keypairstep are intentionally left in place — they will be migrated when next exercised on a real mainnet release.Test Plan
Releaseworkflow againstdevnetfrom this branch.Write program buffer,Upgrade program (devnet),Upload IDL via program-metadata (devnet),Verify build (devnet)all succeed.Failing run for reference: https://github.com/solana-program/subscriptions/actions/runs/25178912188