chore(mise): replace deprecated ubi: prefix by github: prefix

[benoitf]

Summary

Replace deprecated ubi: prefix by github: prefix ¹

When executing the command mise run vm:setup I have an error message

mise ERROR Failed to install ubi:EmbarkStudios/cargo-about@0.8.4: HTTP request to https://api.github.com/repos/EmbarkStudios/cargo-about/releases/tags/v0.8.4 returned an error status

ubi: is assuming the tag has a v prefix but here the tag has not the prefix https://github.com/EmbarkStudios/cargo-about/releases/tag/0.8.4

I'm using mise 2026.4.18 macos-arm64 (2026-04-19)

Related Issue

N/A

Changes

• mise reports that ubi is deprecated and that github backend should be use instead
• using github: prefix allows to give the hint that the tag has not the 'v' prefix for EmbarkStudios/cargo-about

Testing

• mise run pre-commit passes
• Unit tests added/updated
• E2E tests added/updated (if applicable)

Checklist

• Follows Conventional Commits
• Commits are signed off (DCO)
• Architecture docs updated (if applicable)

Footnotes

1. https://mise.jdx.dev/dev-tools/backends/ubi.html↩

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[github-actions]

All contributors have signed the DCO ✍️ ✅
_{Posted by the DCO Assistant Lite bot.}

[pimlock]

Thanks!

[pimlock]

I'm looking into the failing workflow: https://github.com/NVIDIA/OpenShell/actions/runs/24847955299/job/72742796860

[pimlock]

/ok to test 6e8b523

[pimlock]

Thanks again @benoitf.
I will take the sccache migration as a separate item, as turns out it's more involved. I just reverted that back to before my suggestion.

TL;DR it looks like the path to make that work with github backend is provide platform specific patterns: https://mise.jdx.dev/dev-tools/backends/github.html#platform-specific-asset-patterns

I also think that we should consider adding locking to mise, so artifacts for all platforms are resolved at lock time (and we have an extra protection in case an artifact was overriden).

[pimlock]

@benoitf the release job after merging this is failing for unrelated reason, I'm dealing with this as well. Not a happy-CI day today 😅 .

[benoitf]

ah yes :-/ I was not expecting that