Found by a doc-verification pass that executed the build targets (PR #27 review):
`.github/workflows/release-artifacts.yml:68-69` does `cp backend/authproxy dist/` and `cp backend/ocm-secrets dist/`, but the Make targets it depends on output `backend/authproxy-linux` and `backend/ocm-secrets-linux` (`Makefile build-authproxy` / `build-ocm-secrets`). The lane has never run (no `v*` tag has ever been pushed — see #21), so the mismatch is latent; it will fail on the first real tag.
Fix is two path corrections (or `-o` flag alignment). Related: #21 (GCS stays the canonical channel for big artifacts; this lane covers the small Go binaries only), and `make build-ocmptyd` / `install-vm-binaries` were just added in PR #27 — worth deciding whether ocmptyd belongs in the release set too.
🤖 Generated with Claude Code
Found by a doc-verification pass that executed the build targets (PR #27 review):
`.github/workflows/release-artifacts.yml:68-69` does `cp backend/authproxy dist/` and `cp backend/ocm-secrets dist/`, but the Make targets it depends on output `backend/authproxy-linux` and `backend/ocm-secrets-linux` (`Makefile build-authproxy` / `build-ocm-secrets`). The lane has never run (no `v*` tag has ever been pushed — see #21), so the mismatch is latent; it will fail on the first real tag.
Fix is two path corrections (or `-o` flag alignment). Related: #21 (GCS stays the canonical channel for big artifacts; this lane covers the small Go binaries only), and `make build-ocmptyd` / `install-vm-binaries` were just added in PR #27 — worth deciding whether ocmptyd belongs in the release set too.
🤖 Generated with Claude Code