Stefan Walcz fe16ba6f1c fix(gallery): keep the pinned revision's sha256 in the checksum bot ...

The checksum bot dropped the revision from URIs like
.../resolve/<revision>/<file> and asked Hugging Face for the file on
main. When the repo changed a file after the pin, the bot wrote main's
sha256 next to a URI that still downloads the pinned file, so the
install fails the checksum.

That happened in #12989: the eight LFM3-Audio entries download
mmproj-LFM3-Audio-2B-Q8_0.gguf from revision fcfae902, whose sha256 is
26601e90..., but the bot set 2b6648b1... (the file on main). The
gallery test lfm3_audio_entries_test.go caught it and fails on master.

Pass the revision to get_paths_info and hf_hub_download, and restore
the eight checksums.

Docs-Not-Needed: CI helper and gallery data only, no user-facing behaviour changes
Assisted-by: Claude Code:claude-opus-5-5
Signed-off-by: Stefan Walcz <stefan.walcz@walcz.de>

2026-10-31 19:29:43 +01:00

..

index.yaml

fix(gallery): keep the pinned revision's sha256 in the checksum bot

2026-10-31 19:29:43 +01:00