aiken/crates
KtorZ 87087a1811 Always check package status when version is not pinned
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`.
2023-09-13 17:17:32 -04:00
..
aiken feat(cli): add --deny to build, check, and docs 2023-09-06 17:19:44 -04:00
aiken-lang fix: is_record was used incorrectly in code gen, 2023-09-13 00:33:02 -04:00
aiken-lsp chore: Release 2023-08-24 15:05:12 -06:00
aiken-project Always check package status when version is not pinned 2023-09-13 17:17:32 -04:00
flat-rs add tests for case and constr 2023-09-03 11:52:49 -04:00
uplc Fix clippy suggestions. 2023-09-08 16:21:07 +02:00