Can we specify cargo-machete's version on GitHub Actions?

[kyu08]

Hi, thanks for maintaining cool tool!

Can we use specific version of cargo-machete on GitHub Actions?
Currently we can specify the version of workflow but it seems that the latest version of cargo-machete binary is installed.
I would appreciate it if the same behavior could be guaranteed as long as the action version is not changed because it would prevent workflows from suddenly failing when their versions haven't been changed.

name: Detect unused dependencies
on:
  push:
    branches: [ "main" ]
  pull_request:

jobs:
  detect-unused-dependencies:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@v4
      - name: Machete
        uses: bnjbvr/cargo-machete@v0.8.0
          with:
            version: '0.8.0' # or just use the same version of action.

[bnjbvr]

Yep, that sounds great to me! Ideally the version field should support: - no value (in which case it'd select the latest tag/release) - a tagged version - a commit's SHA - `main` (for the main branch). I suppose a good practice is to pin to a specific version or commit SHA these days, so maybe there's little value in this particular option. I'll keep that in mind when working on the rewrite of the action.

[kyu08]

Thanks for the quick response! I'm happy with that you accepted my suggestion.

Ideally the version field should support:

• no value (in which case it'd select the latest tag/release)
• a tagged version
• a commit's SHA
• main (for the main branch). I suppose a good practice is to pin to a specific version or commit SHA these days, so maybe there's little value in this particular option.

Yep, these are reasonable for me as well.
Thank you!