NEARBuilders / NEARBuilders/everything-dev
everything-dev: when out of allowance for deploy, prompt how to re-up
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5
- Forks
- 6
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
During a deploy (like this one), you see:
Error:
0: Error: Access Key <ed25519:6YCW86N8qkTx2nZyKfqs2bJ592BWRSb6dRzi7VQ2eJie> for account <dev.everything.near> does not have enough allowance (0.225561504841242 NEAR) to cover transaction cost (0.300924829803945 NEAR).
Now the key must be deleted first:
near account delete-keys dev.everything.near public-keys ed25519:6YCW86N8qkTx2nZyKfqs2bJ592BWRSb6dRzi7VQ2eJie network-config mainnet
and then create a new one:
bun bos key publish
Contributor guide
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 with the deploy workflow represented by the linked GitHub Actions run and trace where the allowance error is surfaced. Reproduce the out-of-allowance path, then make it show recovery guidance using the delete-keys and bun bos key publish commands; done means deploy users see those instructions instead of only the raw error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bun, typescript
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100