feat: register solana-program-upgrade skill#22
Open
mitgajera wants to merge 1 commit into
Open
Conversation
|
@mitgajera is attempting to deploy a commit to the STBR TRUE Team on Vercel. A member of the Team first needs to authorize it. |
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.
What this adds
Registers solana-program-upgrade as an
ext/submodule skill: an addon tosolana-devthat owns the program-upgrade + on-chain account-migration lifecycle, the most catastrophic and under-tooled step in the Solana dev lifecycle..claude/skills/ext/program-upgrade-> mitgajera/solana-program-upgrade-skill (MIT).claude/skills/skill-registry.jsonentry (domainsolana-infra,install.method: submodule).claude/skills/SKILL.mdunder "Infrastructure & Deployment"Problem it solves
When a team changes an
#[account]struct and redeploys, the new code misreads existing accounts:AccountDidNotDeserialize, wrong values, or silent corruption of user funds. No existing kit skill covers program upgrade plus account-data migration (distinct from/migrate-web3client migration and the basic/deploy). This fills that gap with version-aware, simulate-first guidance:Migration<From, To>type, flagged verify-before-use with the manual pattern as the portable defaultFit
solanaCLI flag verified against the installed binary; the realloc migration snippet compiled (Anchor 0.31, with Anchor 1.0 notes forCpiContext/discriminator); all resource links resolve;Migrationtype treated as verify-before-use.