Second release today. v0.1.2 fixed the build system, and then I actually tried installing the packages it produced. Several of them didn’t work. Everything in this release came from sitting down on real machines and running brew install, dpkg -i, docker run — the things an actual user would do that I’d been skipping.
Fixed release packaging across the board. Shell completions for adze weren’t being included in any of the packages — the installer script copied the binary but skipped the completions directory. The RPM spec had a dependency on a library path that doesn’t exist on Fedora 39+. The Docker image was missing the runtime’s shared libraries. Each of these is a five-minute fix once you know about it, but you only learn about them by installing the packages on actual systems, which I should have been doing earlier. (Should have. Wasn’t.)
Switched macOS notarization from Apple ID to App Store Connect API keys. Apple ID authentication requires interactive 2FA, which doesn’t work in CI. The API key approach uses a .p8 key file and issuer/key IDs, no interaction needed. This had been half-working before — the signing step succeeded but notarization would silently skip when the Apple ID session expired.
Made all non-Linux builds continue-on-error. Previously only Windows had this flag. macOS builds fail often enough from Xcode version mismatches on GitHub’s runners that blocking the release on them wasn’t sustainable.
Fixed CI secret handling. GitHub Actions doesn’t let you reference secrets in if: conditions at the step level — they’re not available in that context, so the condition always evaluates to false. Moved the checks to job-level environment variables where secrets are accessible.
Fixed Homebrew tap push authentication. The default GITHUB_TOKEN can’t push to a different repository. Added the HOMEBREW_TAP_TOKEN PAT.
Resolved codegen test failures and WASM build warnings. Cleanup from the v0.1.2 changes that introduced a few regressions in the C++ test suite.