Fix workflow_dispatch trigger for Winget workflow

[sitiom]

Landing a Pull Request (PR)

I'm not sure why the release trigger did not trigger, but anyhow, I added a tag name input to the workflow_dispatch trigger to fix the workflow failure.

Branching checklist

• There is an issue associated with your PR (bug, feature, etc.. if not, create one)
• Your PR description references the associated issue (i.e. fixes #123456)
• Code is in its own branch
• Branch name is related to the PR contents
• PR targets main

Static analysis checks

• All rust files are formatted using cargo fmt
• All clippy checks pass when running cargo clippy --all-targets --all-features -- -D warnings -A clippy::mutex-atomic
• All existing tests pass

Documentation

• New code is documented using doc comments
• Documentation about your PR is included in the docs, as needed. The docs live in a separate repository. Update the appropriate pages at the links below.
  • update example config file section
  • update help output section
  • add an example
  • update comparison table

Additional Tests

• New code is unit tested
• New code is integration tested, as needed
• New tests pass

[epi052]

appreciate it! I ran out of time to dink with it yesterday and just left it til this morning. The plan was to manually fire it for now and figure out the release trigger later, lol.

Thanks again for the help!

[sitiom]

Now it works: https://github.com/epi052/feroxbuster/actions/runs/9545359358/job/26305946498, but it didn't create the PR since I manually created it earlier: microsoft/winget-pkgs#158049. Let's just see about it on the next release 🙂

[sitiom]

You made a release without any assets? https://github.com/epi052/feroxbuster/actions/runs/10870606291

Anyways, the manual workflow_dispatch worked:

• New version: epi052.feroxbuster version 2.11.0 microsoft/winget-pkgs#173424