A small patch release: remote tasks pinned to a commit SHA no longer panic, and the Fedora COPR packaging pipeline picks up Dockerfile fixes again.
Fixed
-
(task) Remote tasks referenced by commit SHA (a
git::source with?ref=<40-char hex>) no longer crash mise withwe map by name only and have no object-id in refspecfromgix(#9473) by @jdx.gix-refspecparses any 40- or 64-char hex string as anObjectIdrefspec, butgix::clone::fetch::util::find_custom_refnameonly handles name-based matches andexpect()s on the result, so passing a bare SHA toprepare_clone.with_ref_name()triggered a hard process panic on every cache miss.Git::clonenow detects SHA-shaped refs via alooks_like_shaheuristic, skips both thewith_ref_name()andgit clone -bpaths (neither accepts bare SHAs), drops--depth 1since shallow clones may not contain the requested object, and checks out the SHA after the clone via the existing CLI-backed update. Named branches and tags continue to use the existing fast paths. Closes #9472. -
(copr) The
copr-publishworkflow no longer pins a staleghcr.io/jdx/mise:coprimage digest, anddocker.ymlnow rebuilds the:coprimage wheneverpackaging/copr/Dockerfilechanges onmain(#9451) by @bestagi. Previously the workflow kept hittingModuleNotFoundError: No module named 'rich'even after #9421 switchedcopr-clitodnf install, because the hardcoded digest still pointed at the old pip-installed image.
New Contributors
Full Changelog: v2026.4.27...v2026.4.28