release: v0.8.3 — bin-per-target matrix + fix FreeBSD upload path

v0.8.2 shipped 6 of 9 expected release assets. Three silent
"No files were found" upload warnings:

1. `BOOTRISCV64.EFI` + `BOOTLOONGARCH64.EFI` — targets end in
   `-unknown-none[-elf]` (bare-metal), so cargo emits a plain ELF
   named `zamak-uefi` with no `.efi` extension. The `*.efi` glob
   matched nothing. Added a `bin:` key to the matrix and upload
   the exact file per target (`.efi` for UEFI targets, no-ext
   for bare-metal).
2. `zamak-freebsd-x86_64` — the `cp target/release/zamak
   /tmp/zamak-freebsd/` ran inside the `vmactions/freebsd-vm` VM.
   `/tmp` isn't synced back to the runner. `target/` IS (it's
   inside the checkout), so upload directly from
   `target/release/zamak`.

Also added `if-no-files-found: error` to every
`upload-artifact@v4` step so future path drifts fail the job
instead of silently skipping.

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

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

Author: UnbreakableMJ

.forgejo/workflows/release.yml

@@ -19,14 +19,22 @@ jobs:
       fail-fast: false
       matrix:
         include:
+          # `bin` is the exact filename cargo emits:
+          # `*-unknown-uefi` targets produce `.efi`; bare-metal
+          # (`-unknown-none*`) targets produce an ELF with no
+          # extension (just the bin-crate name `zamak-uefi`).
           - target: x86_64-unknown-uefi
             artifact: BOOTX64.EFI
+            bin: zamak-uefi.efi
           - target: aarch64-unknown-uefi
             artifact: BOOTAA64.EFI
+            bin: zamak-uefi.efi
           - target: riscv64gc-unknown-none-elf
             artifact: BOOTRISCV64.EFI
+            bin: zamak-uefi
           - target: loongarch64-unknown-none
             artifact: BOOTLOONGARCH64.EFI
+            bin: zamak-uefi
     # BOOTIA32.EFI (i686-unknown-uefi) is intentionally omitted:
     # zamak-uefi/src/paging.rs `compile_error!`s for
     # `target_arch = "x86"` because the IA-32 paging path was
@@ -46,7 +54,8 @@ jobs:
       - uses: actions/upload-artifact@v4
         with:
           name: ${{ matrix.artifact }}
-          path: target/${{ matrix.target }}/release/*.efi
+          path: target/${{ matrix.target }}/release/${{ matrix.bin }}
+          if-no-files-found: error
 
   # `bios-stage3` (zamak-bios.sys BIOS stage-3 binary) is intentionally
   # not built here. `cargo build -p zamak-bios --release` for the host
@@ -74,6 +83,7 @@ jobs:
         with:
           name: ${{ matrix.name }}
           path: target/release/zamak
+          if-no-files-found: error
 
   # Optional FreeBSD CLI build. Runs through `vmactions/freebsd-vm`,
   # matches the FreeBSD leg of the CI test matrix so the host CLI
@@ -94,12 +104,16 @@ jobs:
           run: |
             . $HOME/.cargo/env
             cargo build -p zamak-cli --release
-            mkdir -p /tmp/zamak-freebsd
-            cp target/release/zamak /tmp/zamak-freebsd/
+      # `vmactions/freebsd-vm@v1` mounts the checkout into the VM
+      # and syncs the workspace back on exit, so the binary built at
+      # `target/release/zamak` ends up at the same relative path on
+      # the runner filesystem. `/tmp` inside the VM is NOT synced —
+      # the previous `cp /tmp/…` attempt silently dropped the artifact.
       - uses: actions/upload-artifact@v4
         with:
           name: zamak-freebsd-x86_64
-          path: /tmp/zamak-freebsd/zamak
+          path: target/release/zamak
+          if-no-files-found: error
 
   publish:
     runs-on: ubuntu-latest

.github/workflows/release.yml

@@ -19,14 +19,22 @@ jobs:
       fail-fast: false
       matrix:
         include:
+          # `bin` is the exact filename cargo emits:
+          # `*-unknown-uefi` targets produce `.efi`; bare-metal
+          # (`-unknown-none*`) targets produce an ELF with no
+          # extension (just the bin-crate name `zamak-uefi`).
           - target: x86_64-unknown-uefi
             artifact: BOOTX64.EFI
+            bin: zamak-uefi.efi
           - target: aarch64-unknown-uefi
             artifact: BOOTAA64.EFI
+            bin: zamak-uefi.efi
           - target: riscv64gc-unknown-none-elf
             artifact: BOOTRISCV64.EFI
+            bin: zamak-uefi
           - target: loongarch64-unknown-none
             artifact: BOOTLOONGARCH64.EFI
+            bin: zamak-uefi
     # BOOTIA32.EFI (i686-unknown-uefi) is intentionally omitted:
     # zamak-uefi/src/paging.rs `compile_error!`s for
     # `target_arch = "x86"` because the IA-32 paging path was
@@ -46,7 +54,8 @@ jobs:
       - uses: actions/upload-artifact@v4
         with:
           name: ${{ matrix.artifact }}
-          path: target/${{ matrix.target }}/release/*.efi
+          path: target/${{ matrix.target }}/release/${{ matrix.bin }}
+          if-no-files-found: error
 
   # `bios-stage3` (zamak-bios.sys BIOS stage-3 binary) is intentionally
   # not built here. `cargo build -p zamak-bios --release` for the host
@@ -74,6 +83,7 @@ jobs:
         with:
           name: ${{ matrix.name }}
           path: target/release/zamak
+          if-no-files-found: error
 
   # Optional FreeBSD CLI build. Runs through `vmactions/freebsd-vm`,
   # matches the FreeBSD leg of the CI test matrix so the host CLI
@@ -94,12 +104,16 @@ jobs:
           run: |
             . $HOME/.cargo/env
             cargo build -p zamak-cli --release
-            mkdir -p /tmp/zamak-freebsd
-            cp target/release/zamak /tmp/zamak-freebsd/
+      # `vmactions/freebsd-vm@v1` mounts the checkout into the VM
+      # and syncs the workspace back on exit, so the binary built at
+      # `target/release/zamak` ends up at the same relative path on
+      # the runner filesystem. `/tmp` inside the VM is NOT synced —
+      # the previous `cp /tmp/…` attempt silently dropped the artifact.
       - uses: actions/upload-artifact@v4
         with:
           name: zamak-freebsd-x86_64
-          path: /tmp/zamak-freebsd/zamak
+          path: target/release/zamak
+          if-no-files-found: error
 
   publish:
     runs-on: ubuntu-latest

CHANGELOG.md

@@ -12,6 +12,32 @@ All dates use ISO 8601 format (YYYY-MM-DD).
 
 ## [Unreleased]
 
+## [0.8.3] - 2026-04-24
+
+Third release-workflow patch. v0.8.2 produced 6/9 expected assets
+on the GH Release page. Three artifacts (`BOOTRISCV64.EFI`,
+`BOOTLOONGARCH64.EFI`, `zamak-freebsd-x86_64`) failed to upload
+with silent `"No files were found"` warnings.
+
+### Fixed
+
+- **`build-artifacts` upload path** — was `*.efi`, but the two
+  bare-metal targets (`riscv64gc-unknown-none-elf`,
+  `loongarch64-unknown-none`) produce a plain ELF named
+  `zamak-uefi` (no `.efi` extension). Added an explicit `bin:`
+  matrix key per target — `zamak-uefi.efi` for the two UEFI
+  targets, `zamak-uefi` for bare-metal — and point the upload
+  at `target/<target>/release/<bin>` exactly.
+- **`cli-freebsd` upload path** — was `/tmp/zamak-freebsd/zamak`,
+  which is VM-internal and not synced back to the runner.
+  `vmactions/freebsd-vm@v1` DOES sync the `target/` directory
+  out (it lives inside the checkout), so upload directly from
+  `target/release/zamak` and drop the no-op `cp` into `/tmp`.
+- **All `upload-artifact@v4` steps** — added
+  `if-no-files-found: error`. Future path drifts will fail the
+  job instead of silently skipping the upload with a warning,
+  so we don't release ship short again without noticing.
+
 ## [0.8.2] - 2026-04-24
 
 Second release-workflow patch. v0.8.1 successfully published a GH

Cargo.lock

@@ -2,7 +2,7 @@
 
 [package]
 name = "zamak-bios"
-version = "0.8.2"
+version = "0.8.3"
 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.2" }
-zamak-theme = { path = "../zamak-theme", version = "0.8.2" }
+zamak-core = { path = "../zamak-core", version = "0.8.3" }
+zamak-theme = { path = "../zamak-theme", version = "0.8.3" }
 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.2"
+version = "0.8.3"
 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.2"
+version = "0.8.3"
 edition = "2021"
 license = "GPL-3.0-or-later"
 
 [dependencies]
-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" }
+zamak-proto = { path = "../zamak-proto", version = "0.8.3" }
+zamak-macros = { path = "../zamak-macros", version = "0.8.3" }
+zamak-theme = { path = "../zamak-theme", version = "0.8.3" }
 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.2"
+version = "0.8.3"
 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.2"
+version = "0.8.3"
 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.2"
+version = "0.8.3"
 edition = "2021"
 description = "Limine Protocol types and request/response structures for ZAMAK"
 license = "GPL-3.0-or-later"