The release-windows.yml workflow failed to run correctly for the 0.8.0 release. On September 24, 2025, run number 17962870805 didn't work. The result was that the git-crypt-0.8.0-x86_64.exe file was never added to the release. That file is very important for Windows users. The 0.7.0 release includes that file. It's absent from 0.8.0.
The run logs have expired. I checked out the 0.8.0 tag on my machine. Building it locally using the exact instructions the workflow uses, MSYS2 MINGW64, installing mingw-w64-x86_64-toolchain and mingw-w64-x86_64-openssl and then running make LDFLAGS="-static-libstdc++ -static -lcrypto -lws2_32 -lcrypt32" works perfectly today. There were no compilation issues. Just a few OpenSSL 3.0 deprecation warnings. When I run git-crypt.exe --version, it correctly reports git-crypt 0.8.0.
The problem was likely a temporary CI issue. Perhaps there was a stale mirror, or an old package version, or something went wrong with the runner image. There doesn't seem to be any indication of a real incompatibility. Could someone rerun the workflow against the existing 0.8.0 release tag? That should attach the missing exe. I am happy to help if it breaks again.
The
release-windows.ymlworkflow failed to run correctly for the 0.8.0 release. On September 24, 2025, run number 17962870805 didn't work. The result was that thegit-crypt-0.8.0-x86_64.exefile was never added to the release. That file is very important for Windows users. The 0.7.0 release includes that file. It's absent from 0.8.0.The run logs have expired. I checked out the 0.8.0 tag on my machine. Building it locally using the exact instructions the workflow uses, MSYS2 MINGW64, installing mingw-w64-x86_64-toolchain and mingw-w64-x86_64-openssl and then running
make LDFLAGS="-static-libstdc++ -static -lcrypto -lws2_32 -lcrypt32"works perfectly today. There were no compilation issues. Just a few OpenSSL 3.0 deprecation warnings. When I rungit-crypt.exe --version, it correctly reports git-crypt 0.8.0.The problem was likely a temporary CI issue. Perhaps there was a stale mirror, or an old package version, or something went wrong with the runner image. There doesn't seem to be any indication of a real incompatibility. Could someone rerun the workflow against the existing 0.8.0 release tag? That should attach the missing exe. I am happy to help if it breaks again.