You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Upload a source tarball as part of the release process, rather than relying on GitHub's automatically generated tarballs. The generated tarballs can cause issues if git attributes change (or other potentially undiscovered shifts), which can break Homebrew releases (with checksum mismatches).
Also update the Homebrew release process to use the uploaded tarball instead of the generated GitHub tarball.
The text was updated successfully, but these errors were encountered:
Michael, I'd like to steal this issue and include it in a batch of release artifact changes I'm planning for zrok and ziti to adopt industry-standard attestations for the release binaries and container images.
Upload a source tarball as part of the release process, rather than relying on GitHub's automatically generated tarballs. The generated tarballs can cause issues if git attributes change (or other potentially undiscovered shifts), which can break Homebrew releases (with checksum mismatches).
Also update the Homebrew release process to use the uploaded tarball instead of the generated GitHub tarball.
The text was updated successfully, but these errors were encountered: