6 ms·

what's the significance of this? There is also a v0.1.1 from 4 hours ago, but these v0.1.x one's are on the releases tab https://github.com/ggml-org/llama.cpp/

• rpdillon 2mo ago
  Yeah, I think they are strays added by GitHub Actions, they don't line up with the actual version that's tracked inside the source code, which indicates v0.20.1: https://github.com/ggml-org/llama.cpp/commit/cea66f4c5a172556362a01b19f875c6093c81986 https://github.com/ggml-org/llama.cpp/commit/cea66f4c5a17255...
  • wccrawford 2mo ago
    2 releases back: ``` Add a "Create and push git tag" step to the release job, right before the "Create release" step. The tag is created with git tag and pushed with the deploy key already configured by the Clone step, instead of relying on the Releases API (action-create-release) to create it as a side effect. The tag is lightweight, matching all existing b release tags. The step is idempotent: if the tag already exists (e.g. on a re-run), creation and push are skipped. ``` I think they just haven't configured the TAG part of that properly yet, so it created an incorrect tag the first run.