solana-foundation / solana-foundation/github-actions
`verify-build` action seems to fall back to default keypair even when `keypair` is set
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 12
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
This issue documents what seems to be happening.
We're invoking the verify-build step with keypair: ${{ env.DEPLOYER_KEYPAIR }}, however, we're getting error Failed to load keypair from path '/home/runner/.config/solana/id.json'. It seems that the build step is falling back to using the default path set by solana config set rather than the provided keypair.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked pull request and the verify-build action's handling of the keypair input. Trace why ${{ env.DEPLOYER_KEYPAIR }} is not used and the default /home/runner/.config/solana/id.json path is selected; done means verification loads the provided keypair instead.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 48/100