chore(deps): bump houseabsolute/actions-rust-cross from 0 to 1 in the dependencies group

[dependabot]

Bumps the dependencies group with 1 update: houseabsolute/actions-rust-cross.

Updates houseabsolute/actions-rust-cross from 0 to 1

Release notes

Sourced from houseabsolute/actions-rust-cross's releases.

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.

v0.0.14 - Install musl-tools if needed

• When the given target includes the string musl, this action will install the musl-tools package. This allows crates with C or C++ code to compile properly. Fixes #20. Reported by Matteo Pietro Dazzi (@​ilteoood).

v0.0.13 - Can install cross from git

• It's now possible to set cross-version to a git ref like a commit hash or HEAD. This will install cross from its git repo.

v0.0.12

• Bumped the version of actions/cache used in this action to v4. The v3 version uses Node 16, which causes warnings when run. Implemented by @​hms5232. GH #13.

v0.0.11

• Use cross when compiling for 32-bit Linux targets. While in theory this should work without cross, compiling openssl with the vendored feature fails when we run cargo build --target i686-unknown-linux-musl.

v0.0.10

• Fixed handling of crates with multiple binaries. Attempting to strip binaries for such a crate caused the build to fail. Reported by Tomaž Hribernik. GH #8
• Added a new cross-version parameter. This can be specified to make this action use a specific version of cross. If this is not specified, the latest version will be used.

v0.0.9

• Added a working-directory parameter. By default this is the current directory (.) but you can set it to something else to compile a single crate or workspace in a subdirectory of the repo. This allows you to use this action with monorepos with multiple crates. Based on GH #7 by @​aaronvg.

v0.0.8

• For builds that need the cross binary, this binary is now cached. A cache hit saves about 20 seconds in my tests. Suggested by @​timon-schelling. GH #4.

v0.0.7

• The toolchain argument was (probably) not being respected with cross builds, though it's hard to be sure since none of the output from past CI runs I've looked at it includes the toolchain version in the output. But now the toolchain version is explicitly passed to all cargo and cross commands.

v0.0.6

• When the strip parameter was true, stripping binaries could fail if there were both target/*/debug and target/*/release directories present and the debug directory didn't have a binary. Now it will strip all binaries it finds under target.

v0.0.5

• Fix use of dtolnay/rust-toolchain action to allow passing a toolchain input.

v0.0.4

• Added a new toolchain parameter to allow selecting a Rust toolchain other than stable. This supports picking on of "stable", "beta", or "nightly".
• Fixed binary stripping to work in more situations. Previously it depended on a very specific setup plus expected to be run in the context of the matrix I use for my own projects.

... (truncated)

Changelog

Sourced from houseabsolute/actions-rust-cross's changelog.

0.0.17 - 2024-11-23

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

0.0.16 - 2024-11-17

• 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.

0.0.15 - 2024-09-21

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

0.0.14 - 2024-08-25

• When the given target includes the string musl, this action will install the musl-tools package. This allows crates with C or C++ code to compile properly. Fixes #20. Reported by Matteo Pietro Dazzi (@​ilteoood).

0.0.13 - 2024-05-18

• It's now possible to set cross-version to a git ref like a commit hash or HEAD. This will install cross from its git repo.

0.0.12 - 2024-02-25

• Bumped the version of actions/cache used in this action to v4. The v3 version uses Node 16, which causes warnings when run. Implemented by @​hms5232. GH #13.

0.0.11 - 2023-12-17

• Use cross when compiling for 32-bit Linux targets. While in theory this should work without cross, compiling openssl with the vendored feature fails when we run cargo build --target i686-unknown-linux-musl.

0.0.10 - 2023-12-10

• Fixed handling of crates with multiple binaries. Attempting to strip binaries for such a crate caused the build to fail. Reported by Tomaž Hribernik. GH #8
• Added a new cross-version parameter. This can be specified to make this action use a specific version of cross. If this is not specified, the latest version will be used.

0.0.9 - 2023-09-10

• Added a working-directory parameter. By default this is the current directory (.) but you can set it to something else to compile a single crate or workspace in a subdirectory of the repo. This allows you to use this action with monorepos with multiple crates. Based on GH #7 by @​aaronvg.

... (truncated)

Commits

• 7180715 Don't try to install musl-tools if it's already installed
• a1777f5 Add first step to print all inputs
• b1824d4 Update README.md for version 1 bump
• 3d79b24 Rename os to runs-on in test matrix workflow
• 9ec7e60 Clarify use cases in README.md
• fd3526d Fix example in README.md to use checkout@v4
• 12331c3 Tweak wording in README.md
• dbeb1eb Replace all Perl scripts with Rust
• dad7ec1 Validate inputs to this action
• 0264056 Add bench to command docs
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions