Align orchestration with the solana-program org - #19
Merged
Conversation
lorisleiva
marked this pull request as ready for review
June 10, 2026 08:32
joncinque
approved these changes
Jun 10, 2026
joncinque
left a comment
joncinque
left a comment
There was a problem hiding this comment.
Looks great! Also added a branch protection rule so we can auto-merge
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
2 participants
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.
Aligns this repo's CI and orchestration with the other repos in the solana-program org. It replaces the bespoke GitHub workflows and zx scripts with a
Makefileplus the reusablesolana-program/actionsworkflows, relocates the IDL to the repo root (idl.json), wirescodama.mjsto read the toolchain from the Makefile, and slims the root tooling. The JS tests already run against LiteSVM in-process, so no validator is involved.Note: the publish workflow now targets the reusable flow, which requires the GitHub App (
vars.APP_ID/secrets.PRIVATE_KEY) and NPM provenance to be provisioned before the next publish. CI (main.yml) is unaffected.