llama.cpp : bump version to 0.6.0 (#29997)

* llama.cpp : bump version to 0.6.0 * scripts : update summary prompt (#0)
2026-10-05 18:13:51 +03:00
parent 4d60b4d087
commit d812350493
2 changed files with 4 additions and 2 deletions
@@ -4,7 +4,7 @@ include(CheckIncludeFileCXX)

 ### llama.cpp version
 set(LLAMA_VERSION_MAJOR 0)
-set(LLAMA_VERSION_MINOR 5)
+set(LLAMA_VERSION_MINOR 6)
 set(LLAMA_VERSION_PATCH 0)
 set(LLAMA_VERSION_BASE "${LLAMA_VERSION_MAJOR}.${LLAMA_VERSION_MINOR}.${LLAMA_VERSION_PATCH}")

@@ -44,10 +44,12 @@ Write a summary of the change log in a few sections:
 Guidelines:

 - All bullet point in the summary should be concise and rarely exceed a single line of 120 characters (excluding PR links)
+- Do not wrap or break lines within a bullet point or paragraph - each bullet point must fit on a single line (PR links allowed to exceed the line limit)
 - Avoid repeating `ggml`-specific changes - these should already be covered by the `ggml` release links
 - Provide PR link for each bullet point where possible
 - Don't add bullet point to state that there are no API changes in some module
- Combine related topics (a full list of commits will be appended independently at end of the summary)
+- Group similar/related items into a single bullet with multiple trailing PR links, one bullet per topic
+  - A full list of commits will be appended independently at end of the summary, so it is not a problem to skip some less important changes
 - Skip minor-impact notes (e.g. "fix compile warnings", "refactored code", ...)

 Output just the summary in a markdown block, without any extra text. Save it to a local text file called `release-notes-vX.Y.Z.txt`.