v1.0.5

• Fixed a bug in the handling of the rust-cache-parameters input. If anything was specified for this, it would end up providing a broken config to the Swatinem/rust-cache action. Reported by @SinTan1729 (Sayantan Santra). GH #46.

v1.0.4

• Removed validation for the toolchain input. The dtolnay/rust-toolchain accepts a lot of different options that this action wasn't allowing. It's simpler and more flexible to just let that action handle validation. Requested by @axos88 (Akos Vandra-Meyer). GH #42.
• Removed validation for the command input. This allows you to use this action with any cargo extension command, like cargo-deb. Setting command to both is still supported and will run the build and test commands. Requested by @bvaisvil (Benjamin Vaisvil). GH #43.

v1.0.3 - Partial support for Linux ARM hosts

• Fixed a bug when running with a Linux ARM host where the action would use a cached cross download for x86-64 Linux (or vice versa). Now the cache key for the cross binary includes both the runner's architecture in addition to its OS.
• This release partially support running on Linxu ARM, but see the README.md file for details on this.

v1.0.2 - `force-use-cross` input

• Added a new force-use-cross input, which does what it says. It will force the use of cross even when it is not required for given platform/target combination. Note that this only works on Linux hosts.

v1.0.1

• Fixed a bug where this action would attempt to use cross when compiling for an ARM Linux target on an ARM Linux host.

v1.0.0

The addition of caching is a significant behavior change for this action, so the version has been
bumped to v1.0.0 because of this change.

• This action will now configure and use Swatinem/rust-cache by default for you. It will include the target parameter as part of the cache key automatically, as well as the OS version when using cargo on Linux. Suggested by @jennydaman (Jennings Zhang). GH #23.
• This action now validates its input and will exit early if they are not valid. GH #35.
• When compiling for musl targets, this action will not try to reinstall the musl-tools package if it's already installed.

The following changes were made since the 1.0.0-beta1 release:

• The cache key includes information that causes the cache to not be re-used when the system running cargo or cross changes. When using cargo on Linux, this is the OS version, like "Ubuntu 22.04". When using cross, this is the hash of the cross binary itself. This is needed because the Docker images that cross uses can change when the binary is updated. This can include changing the underlying Docker image base OS, in which case it's quite likely the old cache contents would be incompatible with the the new image.

v1.0.0 Beta 1 - Now with caching built in

The addition of caching is a significant behavior change for this action, so the version has been
bumped to v1.0.0 because of this change.

• This action will now configure and use Swatinem/rust-cache by default for you. It will include the target parameter as part of the cache key automatically. Suggested by @jennydaman (Jennings Zhang). GH #23.
• This action now validates its input and will exit early if they are not valid. GH #35.

v0.0.17 - `bench` command

• Added support for running cargo bench or cross bench. Implemented by @RaulTrombin (Raul Victor Trombin). GH #32.

v0.0.16

• Arguments passed in the args parameter are now always last when executing cargo. This lets you pass arguments to test binaries like -- --something. First reported by @mateocabanal (Mateo Cabanal) as GH #12 and fully fixed by @donatello (Aditya Manthramurthy) in GH #30.

v0.0.15 - Only install musl packages when needed

• The musl packages are only installed when not cross-compiling.