Releases: baptiste0928/cargo-install
Releases · baptiste0928/cargo-install
v3.3.0
Changed
- Removed the job id from the cache key. This allows the same cache to be used across multiple jobs if the installation arguments are the same.
- Improved the cache key generation logic.
v3.2.0
Warning
Versions prior to v3.2 will stop working on February 1st, 2025, due to GitHub changing their cache service APIs. See also the @actions/cache
package deprecation notice.
Changed
- Updated to
@actions/cache
v4.
v3.1.1
Fixed
- Pre-release versions are ignored when resolving the latest version.
v3.1.0
Changed
- Runner arch is included in the cache key.
Fixed
- Fix runner os version resolution on macOS runners. (issue #24)
v3.0.1
Fixed
- Improve git tag/branch resolution. (issue #22)
v3.0.0
Added
- Runner os version is included in the cache key. (#21)
Changed
- Breaking: The action now runs on Node.js 20.
- Dependencies have been updated.
v2.2.0
Added
- Support alternative registries with the
registry
andindex
input parameters.
Changed
- Crate versions are fetched from the sparse index instead of the crates.io API.
v2.1.0
Added
- Git installation is now supported with the
git
input parameter. You can specify a branch, tag or commit hash. (#14)
Usage:
- name: Install cargo-sort from git
uses: baptiste0928/cargo-install@v2
with:
crate: cargo-sort
git: https://github.com/devinr528/cargo-sort
tag: v1.0.9 # `branch` and `commit` are also supported
v2.0.0
✨ New major release. This new version should remove the warning about Node 12 being deprecated, along with some improvements to the default behaviour. I also rewrote and improved most of the code.
Added
- Name and version are shown in the cache key. This allows to identify cache
entries in the cache management UI more easily.
Changed
- Breaking: The action now runs on Node.js 16.
- Breaking: Versions without semver range (e.g.
1.2.3
) are now considered
as exact versions. - Breaking: Set
--locked
by default.locked
input is no longer
deprecated. - Various code improvements and refactoring.
v1.3.1
Fixed
- Use
semver
instead ofcompare-versions
to fix version resolution issues. - Dependencies have been updated. This removes the warning about
set-output
being deprecated.