mirror of
https://github.com/DeusData/codebase-memory-mcp.git
synced 2026-11-07 08:43:35 +08:00
Martin Vogel
4fac943314
Two release-blockers surfaced once #882 made every smoke leg a required gate (continue-on-error previously masked them): - smoke-unix ran the *dynamic* linux binary on ubuntu-22.04 / 22.04-arm, where it cannot start (it links glibc 2.38+) -> Phase 1 died. Older-glibc coverage is the -portable (static) binary's job and is green via the smoke-linux-portable broad legs, so drop the impossible dynamic broad legs (keep macOS). - the ClamAV scan died on every linux leg: apt auto-starts the clamav-freshclam daemon which holds the freshclam log lock, so the manual freshclam failed with "Failed to lock the log file ... Resource temporarily unavailable". Stop the daemon first. Also add native ARM64 Windows as a first-class release target -- the one platform we test (windows-11-arm) but never shipped: - build-windows-arm64 job (CLANGARM64) producing codebase-memory-mcp[-ui]-windows-arm64.zip - smoke-windows is now arch-aware: windows-11-arm smokes the NATIVE arm64 binary instead of the x86_64 binary under emulation - a native soak-quick-windows-arm64 leg (no sanitizer -- ASan is unavailable on native ARM64 Windows) - arm64 detection in install.ps1 release.yml already publishes windows-arm64 (asset filter + merge-multiple) and build_update_url/detect_arch already resolve it; npm/pip/install.sh compute arm64 already. scoop/winget/chocolatey per-version manifests are updated at release time. Signed-off-by: Martin Vogel <martin.vogel.tech@gmail.com>