build(deps): bump Swatinem/rust-cache from 1 to 2

[dependabot]

Bumps Swatinem/rust-cache from 1 to 2.

Release notes

Sourced from Swatinem/rust-cache's releases.

v2.0.0

• The action code was refactored to allow for caching multiple workspaces and different target directory layouts.
• The working-directory and target-dir input options were replaced by a single workspaces option that has the form of $workspace -> $target.
• Support for considering env-vars as part of the cache key.
• The sharedKey input option was renamed to shared-key for consistency.

v1.4.0

• Clean both debug and release target directories.

v1.3.0

• Use Rust toolchain file as additional cache key.
• Allow for a configurable target-dir.

v1.2.0

• Cache ~/.cargo/bin.
• Support for custom $CARGO_HOME.
• Add a cache-hit output.
• Add a new sharedKey option that overrides the automatic job-name based key.

v1.1.0

• Add a new working-directory input.
• Support caching git dependencies.
• Lots of other improvements.

v1.0.1

• Improved logging output.
• Make sure to consider all-features dependencies when pruning.
• Work around macOS cache corruption.
• Remove git-db cache for now.

Changelog

Sourced from Swatinem/rust-cache's changelog.

Changelog

2.7.3

• Work around upstream problem that causes cache saving to hang for minutes.

2.7.2

• Only key by Cargo.toml and Cargo.lock files of workspace members.

2.7.1

• Update toml parser to fix parsing errors.

2.7.0

• Properly cache trybuild tests.

2.6.2

• Fix toml parsing.

2.6.1

• Fix hash contributions of Cargo.lock/Cargo.toml files.

2.6.0

• Add "buildjet" as a second cache-provider backend.
• Clean up sparse registry index.
• Do not clean up src of -sys crates.
• Remove .cargo/credentials.toml before saving.

2.5.1

• Fix hash contribution of Cargo.lock.

2.5.0

• feat: Rm workspace crates version before caching.
• feat: Add hash of .cargo/config.toml to key.

2.4.0

• Fix cache key stability.
• Use 8 character hash components to reduce the key length, making it more readable.

2.3.0

• Add cache-all-crates option, which enables caching of crates installed by workflows.

... (truncated)

Commits

• 23bce25 2.7.3
• 378c828 Work around upstream GitHub issue and update dependencies
• a226033 2.7.2
• d30f114 Only key by Cargo.toml and Cargo.lock files of workspace members (#180)
• b1db5f9 Update action runtime to node20 (#175)
• 3cf7f8c 2.7.1
• e03705e changelog
• b86d1c6 bump all the other dependencies too
• f27990c Update Dependencies (#172)
• a95ba19 2.7.0
• 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 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)

[bbortt]

@dependabot recreate

[github-actions]

🎉 This issue has been resolved in version 1.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀