Need Exact Version Pinning

[matthewkelley22]

tl;dr

Modify dependency in Cargo.toml to

vstd = "=0.0.0-2026-03-17-2326"

Issue

1. Create a new crate and add the following to Cargo.toml:

vest_lib = "0.0.4"

2. Run cargo tree

You'll see that the downloaded vstd version is much newer than the March 17th version used in Vest v0.0.4.

Cause

It seems that vstd violating SymVer while including 0.0.0 as part of its version info is confusing Cargo. Likely, Cargo thinks the current version on crates.io is equivalent to the specified March 17th version.

Solution

Specify = before the version of vstd in Cargo.toml (as in the tl;dr section).

Currently, this can be fixed for end users if they specify an exact vstd version before listing vest_lib as a dependency (see below), but that shouldn't be a long-term solution.

vstd = "=0.0.0-2026-03-17-2326"
vest_lib = "=0.0.4"

[y1ca1]

Fixed as part of #45.