[GH-ISSUE #9132] The v0.5.11 release is an unsigned commit #5939

Open
opened 2026-04-12 17:17:01 -05:00 by GiteaMirror · 0 comments
Owner

Originally created by @vt-alt on GitHub (Feb 15, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/9132

When building a package for ALT Linux, I noticed that the v0.5.10 and v0.5.11 releases are unsigned commits. (They also lack the green checkmark icon on the Releases page.) Meanwhile, v0.5.8 and v0.5.9 are signed commits.

Can you start signing release commits again? (I would prefer signed annotated tags by a real person, though). Even though this is just the generic GitHub web-flow key, it's useful for (best effort) verifying the supply chain.

Originally created by @vt-alt on GitHub (Feb 15, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/9132 When building a package for ALT Linux, I noticed that the v0.5.10 and v0.5.11 releases are unsigned commits. (They also lack the green checkmark icon on the Releases page.) Meanwhile, v0.5.8 and v0.5.9 are signed commits. Can you start signing release commits again? (I would prefer signed annotated tags by a real person, though). Even though this is just the generic GitHub web-flow key, it's useful for (best effort) verifying the supply chain.
GiteaMirror added the feature request label 2026-04-12 17:17:01 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#5939