87087a1811
When the version isn't a git sha or a tag, we always check that we got the last version of a particular dependency before building. This is to avoid those awkward moments where someone try to use something from the stdlib that is brand new, and despite using 'main' they get a strange build failure regarding how it's not available. An important note is that we don't actually re-download the package when the case occurs; we merely check an HTTP ETag from a (cheap) 'HEAD' request on the package registry. If the tag hasn't changed then that means the local version is correct. The behavior is completely bypassed if the version is specified using a git sha or a tag, as here, we can assume that fetching it once it enough (and that it can change). If a package maintainer force-pushed a tag however, there may be discrepency and the only way around that is to `rm -r ./build`. |
||
|---|---|---|
| .. | ||
| src | ||
| templates | ||
| Cargo.toml | ||
| README.md | ||
README.md
Project
This crate encapsulates the code used to manage Aiken projects. See crates/cli for usage.