Bump Dependencies fails with "choco-jom" error

[pljones]

Describe the bug

The bump dependencies Github workflow, triggered after a merge to main, is currently failing reliably.

Note

VSCode Github CoPilot summary of problem

Short summary

The failure is in the dependency-bump automation, not in Jamulus itself. In bump-dependencies.yml, the choco-jom check is using a brittle version lookup against Chocolatey, and that lookup is no longer returning the expected version string. The fix should be to update that workflow step to retrieve the latest jom version from a reliable source or with more robust parsing, and to make the workflow handle empty/missing results gracefully so the bump job does not fail outright.

---

The expected solution is to use a similar process as used for maintaining versions of other tools (e.g. dependabot alerts/PRs).

Example failures:

• https://github.com/jamulussoftware/jamulus/actions/runs/31315655157/job/93250353220
• https://github.com/jamulussoftware/jamulus/actions/runs/31316552439/job/93252636926
• https://github.com/jamulussoftware/jamulus/actions/runs/31317745101/job/93255615411

To Reproduce

Merge a branch to main.

Expected behavior

Bump dependencies should trigger and run cleanly.

Additional context

Github CoPilot analysis of the failure is here:
https://github.com/copilot/share/c85e40b6-03e0-8884-8143-a44984c86055