Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Proposal] Consider using semantic versioning for releasing this library #1065

Closed
facundoolano opened this issue Sep 12, 2022 · 0 comments
Closed

Comments

@facundoolano
Copy link

💥 Proposal

The users of this library (notably aleo and SnarkOS) are currently specifying snarkVM as a dependency by using a commit hash. This is incovenient since not only all users of the library need to update on each snarkVM merge, but also because it's very hard to keep track when a given change is being included or not (and whether a rev is newer or older than another). Additionally, at least until recently pulling dependencies by revision may be slower.

Semver could be used instead, doing explicit github releases or git tagging, improving dependency readability even if locks would still need to be updated to fetch the latest version. A lighter-weight, although more fragile, alternative to consider is to just point the user projects to the main branch of this repository.

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

No branches or pull requests

2 participants