baptiste0928/cargo-install

Planned features for cargo-install v2

baptiste0928 opened this issue · 4 comments

I plan to work on a new major release (with breaking changes) soon.

  • Use exact crate version if full version specified. See #7.
  • Support installing multiple crates at once. See #4.
  • Set locked to true by default to prevent sudden CI failures.
  • Update to Node.js v16.

Use exact crate version if full version specified (e.g 0.5.2 => =0.5.2, 0.5 => ^0.5).

Please don't do this based on the length of the version number

In what situations do you think this would be a bad idea? The current behavior (always default to ^) can cause CI breakages even if a fixed version is not specified. This behavior can be overwritten by specifying an explicit semver range.

I just prefer not having implicit behaviour, so IMO without a prefix the two should behave the same

Could also throw an error if there's no prefix and the version number is not exact