build(deps): bump houseabsolute/actions-rust-cross from 0 to 1

[dependabot]

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

1.0.6 2026-03-15

• Updated various actions used by this action so that it no longer triggers warnings about Node.js 20 deprecation.
• Added a section to the docs about dealing with a failure to link -lexecinfo on NetBSD.

1.0.5 - 2025-07-20

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

1.0.4 - 2025-04-12

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

1.0.3 - 2025-02-17

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

1.0.2 - 2025-02-16

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

1.0.1 - 2025-01-20

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

1.0.0 - 2025-01-11

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.

... (truncated)

Commits

• 576730d Set permissions to contents: read for all workflows
• 08a0dd9 Update Cargo.lock for test code to get rid of security warnings
• a8cc74d Add changes and release date for 1.0.6
• 20562ba Use latest cross HEAD for NetBSD in tests and add this workaround to `READM...
• ac23338 Update various actions to new versions to get rid of Node 20 warnings
• ba9674c Update precious config and fix new linting issues
• bad2d2d Remove unused perltidyrc file
• 9d54e66 Update all dev tools in mise.toml
• ebd8787 Update actions/checkout to v6
• d5793ed Upgrade all Rust dependencies
• 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)