Skip to content

Conversation

@Arrowana
Copy link
Contributor

@Arrowana Arrowana commented Jan 16, 2025

Problem

Picking a solana cli version that is <= makes verifying dependent on the solana-verify version installed

Solution

Strict solana-cli version

@ngundotra
Copy link
Collaborator

Thanks for PR! This is great idea.

In order to be backwards compatible, what if we made this only accessible through new solana-verify argument --strict ?

@Arrowana
Copy link
Contributor Author

Arrowana commented Jun 16, 2025

Thanks for PR! This is great idea.

In order to be backwards compatible, what if we made this only accessible through new solana-verify argument --strict ?

I believe given the goal of this tool not being strict is a bug, adding the flag make it more cumbersome for standard use: strict verification

I hit myself another case of building with wrong cli today

Unable to find docker image for Solana version 2.2.1
Using backup docker image for Solana version 2.1.13
...

@Arrowana Arrowana force-pushed the feat/strict-solana-cli-version branch from f7992cd to b0e8d18 Compare June 16, 2025 00:28
@swaroop-osec
Copy link
Collaborator

lgtm!

@ngundotra ngundotra merged commit 8931df8 into Ellipsis-Labs:master Jun 17, 2025
8 checks passed
@Arrowana Arrowana deleted the feat/strict-solana-cli-version branch June 17, 2025 21:19
@oubiad
Copy link

oubiad commented Jul 1, 2025

Agree

@oubiad
Copy link

oubiad commented Jul 1, 2025

projectserum/build@sha256:75b75eab447ebcca1f471c98583d9b5d82c4be122c470852a022afcf9c98bead

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants