chore: move lazer contract tests out of pnpm test #2437
Merged
Conversation
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
3 Skipped Deployments
|
ali-behjati
approved these changes
Feb 28, 2025
cprussin
approved these changes
Feb 28, 2025
Riateche
force-pushed
the
ci-lazer-contract-no-npm
branch
2 times, most recently
from
e70f195 to
da828fb
Compare
Riateche
force-pushed
the
ci-lazer-contract-no-npm
branch
from
da828fb to
412702e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Summary
Move anchor tests back to a separate workflow.
Rationale
Solana contract brings too many new dependencies (Rust, Solana SDK, anchor) to
pnpm testso it complicates the setup process for pnpm users a lot.How has this been tested?
Adjusted CI tests.