From 4dd5f0e458813d945f1b84158a1603231a73dfae Mon Sep 17 00:00:00 2001
From: preslavmihaylov <preslav@pmihaylov.com>
Date: Mon, 5 Oct 2026 10:05:39 +0300
Subject: [PATCH] kernel: name each release guest-kernel-<version>

---
 .github/workflows/kernel.yml | 2 +-
 docs/kernel.md               | 5 +++--
 2 files changed, 4 insertions(+), 3 deletions(-)

diff --git a/.github/workflows/kernel.yml b/.github/workflows/kernel.yml
index 9b8402891..f34abe8ec 100644
--- a/.github/workflows/kernel.yml
+++ b/.github/workflows/kernel.yml
@@ -68,4 +68,4 @@ jobs:
         run: |
           tag=$(go run ./packaging/kernel/tag)
           cat dist/*.sha256 > dist/SHA256SUMS
-          gh release create "$tag" --target "$GITHUB_SHA" --title "guest kernel $tag" --latest=false --notes "Built by the kernel workflow from packaging/kernel. Reproducible: each file was built twice." dist/Image-arm64 dist/vmlinux-amd64 dist/SHA256SUMS
+          gh release create "$tag" --target "$GITHUB_SHA" --title "guest-$tag" --latest=false --notes "Built by the kernel workflow from packaging/kernel. Reproducible: each file was built twice." dist/Image-arm64 dist/vmlinux-amd64 dist/SHA256SUMS
diff --git a/docs/kernel.md b/docs/kernel.md
index 195384290..19c4c1626 100644
--- a/docs/kernel.md
+++ b/docs/kernel.md
@@ -43,8 +43,9 @@ with Docker builds it faster.
 The `kernel` workflow (`.github/workflows/kernel.yml`) runs on manual dispatch only. It builds each
 arch twice and compares the hashes. It checks them against the hashes that `services/kernel` was
 built with, then publishes `Image-arm64`, `vmlinux-amd64` and `SHA256SUMS` under the release tag
-`kernel-<version>-<build>`. A hash that does not match what the Go code expects fails the workflow,
-so a release can never carry a kernel that the daemon would refuse.
+`kernel-<version>-<build>`, titled `guest-kernel-<version>-<build>`. A hash that does not match what
+the Go code expects fails the workflow, so a release can never carry a kernel that the daemon would
+refuse.
 
 When the daemon creates a microVM provider, it checks the kernel file for the host arch. On first
 use, it fetches the file into `<root>/kernel/<tag>/` and fsyncs the file and its directory. At this