release: v0.8.2 — fix flatten step to rename by upload-name

v0.8.1 successfully published a GH Release but only 4 of the 9
expected assets appeared. The flatten step moved the inner file
of each downloaded artifact (always named `zamak-uefi.efi` or
`zamak`) into `flat/`, so every BOOT*.EFI collapsed to
`zamak-uefi.efi` and every CLI binary to `zamak`, overwriting
each other. Only the last-moved EFI + CLI + SHA256SUMS + SBOM
landed on the release page.

Fix: walk `dist/<upload-name>/` directories, pick the single
inner file per matrix entry, copy to `flat/<upload-name>`. Now
BOOTX64.EFI / BOOTAA64.EFI / BOOTRISCV64.EFI /
BOOTLOONGARCH64.EFI / zamak-linux-x86_64 / zamak-macos-aarch64
/ zamak-freebsd-x86_64 all appear as distinct assets.

11 workspace crates bumped 0.8.1 → 0.8.2. No code changes.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: UnbreakableMJ

.forgejo/workflows/release.yml

@@ -113,14 +113,24 @@ jobs:
         with:
           path: dist
       - uses: dtolnay/rust-toolchain@stable
-      - name: flatten artifact directories
+      - name: flatten + rename artifact directories
         # Each artifact was uploaded under its own subdir
-        # (dist/<name>/<file>). Flatten to dist/<file> so release
-        # assets have the expected short names.
+        # (dist/<upload-name>/<inner-file>). The inner file has the
+        # generic target name (e.g. `zamak-uefi.efi`, `zamak`), so
+        # multiple entries from the same matrix collapse to the same
+        # name if we just flatten. Rename each to its upload-name so
+        # BOOTX64.EFI, BOOTAA64.EFI, zamak-linux-x86_64, … appear as
+        # distinct GH release assets.
         run: |
           set -euo pipefail
           mkdir -p flat
-          find dist -type f -exec mv {} flat/ \;
+          for dir in dist/*/; do
+            upload_name=$(basename "$dir")
+            inner_file=$(find "$dir" -maxdepth 1 -type f | head -1)
+            if [ -n "$inner_file" ]; then
+              cp "$inner_file" "flat/${upload_name}"
+            fi
+          done
           rm -rf dist
           mv flat dist
           ls -la dist

.github/workflows/release.yml

@@ -113,14 +113,24 @@ jobs:
         with:
           path: dist
       - uses: dtolnay/rust-toolchain@stable
-      - name: flatten artifact directories
+      - name: flatten + rename artifact directories
         # Each artifact was uploaded under its own subdir
-        # (dist/<name>/<file>). Flatten to dist/<file> so release
-        # assets have the expected short names.
+        # (dist/<upload-name>/<inner-file>). The inner file has the
+        # generic target name (e.g. `zamak-uefi.efi`, `zamak`), so
+        # multiple entries from the same matrix collapse to the same
+        # name if we just flatten. Rename each to its upload-name so
+        # BOOTX64.EFI, BOOTAA64.EFI, zamak-linux-x86_64, … appear as
+        # distinct GH release assets.
         run: |
           set -euo pipefail
           mkdir -p flat
-          find dist -type f -exec mv {} flat/ \;
+          for dir in dist/*/; do
+            upload_name=$(basename "$dir")
+            inner_file=$(find "$dir" -maxdepth 1 -type f | head -1)
+            if [ -n "$inner_file" ]; then
+              cp "$inner_file" "flat/${upload_name}"
+            fi
+          done
           rm -rf dist
           mv flat dist
           ls -la dist

CHANGELOG.md

@@ -12,6 +12,32 @@ All dates use ISO 8601 format (YYYY-MM-DD).
 
 ## [Unreleased]
 
+## [0.8.2] - 2026-04-24
+
+Second release-workflow patch. v0.8.1 successfully published a GH
+Release but only 4 of the expected 9 assets appeared: the
+`flatten` step renamed all files to their inner basenames
+(`zamak-uefi.efi` for every EFI target, `zamak` for every CLI
+target), so `dist/BOOTX64.EFI/zamak-uefi.efi` and
+`dist/BOOTAA64.EFI/zamak-uefi.efi` both became `flat/zamak-uefi.efi`
+and overwrote each other during the move.
+
+### Fixed
+
+- **`release.yml` flatten/rename step** — now walks
+  `dist/<upload-name>/` directories, picks the single inner file
+  per matrix entry, and copies it to `flat/<upload-name>`. So
+  `BOOTX64.EFI`, `BOOTAA64.EFI`, `BOOTRISCV64.EFI`,
+  `BOOTLOONGARCH64.EFI`, `zamak-linux-x86_64`,
+  `zamak-macos-aarch64`, `zamak-freebsd-x86_64` all appear as
+  distinct release assets.
+
+### Note
+
+v0.8.1's GH Release page will stay on the repo for historical
+reference but is incomplete (4/9 assets). Use v0.8.2 as the
+effective "0.8" release point.
+
 ## [0.8.1] - 2026-04-24
 
 Release-workflow patch release. No code changes; fixes

Cargo.lock

@@ -2,7 +2,7 @@
 
 [package]
 name = "zamak-bios"
-version = "0.8.1"
+version = "0.8.2"
 edition = "2021"
 license = "GPL-3.0-or-later"
 
@@ -13,8 +13,8 @@ license = "GPL-3.0-or-later"
 smp = []
 
 [dependencies]
-zamak-core = { path = "../zamak-core", version = "0.8.1" }
-zamak-theme = { path = "../zamak-theme", version = "0.8.1" }
+zamak-core = { path = "../zamak-core", version = "0.8.2" }
+zamak-theme = { path = "../zamak-theme", version = "0.8.2" }
 log = "0.4"
 x86_64 = { version = "0.15", default-features = false, features = ["instructions"] }
 limine-protocol = "0.5"

zamak-bios/Cargo.toml

@@ -2,7 +2,7 @@
 
 [package]
 name = "zamak-cli"
-version = "0.8.1"
+version = "0.8.2"
 edition = "2021"
 description = "Host-side CLI tool for ZAMAK bootloader (MBR install, config enrollment, SBOM)"
 license = "GPL-3.0-or-later"

zamak-cli/Cargo.toml

@@ -2,14 +2,14 @@
 
 [package]
 name = "zamak-core"
-version = "0.8.1"
+version = "0.8.2"
 edition = "2021"
 license = "GPL-3.0-or-later"
 
 [dependencies]
-zamak-proto = { path = "../zamak-proto", version = "0.8.1" }
-zamak-macros = { path = "../zamak-macros", version = "0.8.1" }
-zamak-theme = { path = "../zamak-theme", version = "0.8.1" }
+zamak-proto = { path = "../zamak-proto", version = "0.8.2" }
+zamak-macros = { path = "../zamak-macros", version = "0.8.2" }
+zamak-theme = { path = "../zamak-theme", version = "0.8.2" }
 limine-protocol = "0.5"
 goblin = { version = "0.7", default-features = false, features = ["elf64", "elf32", "endian_fd", "alloc"] }
 

zamak-core/Cargo.toml

@@ -2,7 +2,7 @@
 
 [package]
 name = "zamak-decompressor"
-version = "0.8.1"
+version = "0.8.2"
 edition = "2021"
 description = "BIOS stage2 decompressor — inflates zamak-bios.sys to a fixed physical address"
 license = "GPL-3.0-or-later"

zamak-decompressor/Cargo.toml

@@ -2,7 +2,7 @@
 
 [package]
 name = "zamak-macros"
-version = "0.8.1"
+version = "0.8.2"
 edition = "2021"
 description = "Procedural macros for ZAMAK bootloader safety annotations"
 license = "GPL-3.0-or-later"

zamak-macros/Cargo.toml

@@ -2,7 +2,7 @@
 
 [package]
 name = "zamak-proto"
-version = "0.8.1"
+version = "0.8.2"
 edition = "2021"
 description = "Limine Protocol types and request/response structures for ZAMAK"
 license = "GPL-3.0-or-later"