Summary
Periphery is advertised as supporting macOS | Linux, but the GitHub release assets for the latest release are macOS-only. This breaks Linux installs for tools that consume GitHub releases directly.
What I observed
For 3.7.4 the latest release currently contains:
periphery-3.7.4.zip
periphery-3.7.4.artifactbundle.zip
After inspecting those assets:
periphery-3.7.4.zip contains periphery, libIndexStore.dylib, LICENSE.md
file periphery reports a Mach-O universal binary
periphery-3.7.4.artifactbundle.zip contains only a periphery-3.7.4-macos/... directory
So there doesn't seem to be any Linux release artifact right now.
Impact
In our CI we install Periphery on Ubuntu via a tool that consumes GitHub release assets. It resolves the Linux platform to:
https://github.com/peripheryapp/periphery/releases/download/3.7.4/periphery-3.7.4.zip
But that zip contains a macOS binary, so on Ubuntu it fails immediately:
/home/admin/.local/share/.../periphery: 3: Syntax error: "(" unexpected
The problem is not Periphery's Linux support itself, but that the published release assets are macOS-only.
Request
Would you consider publishing Linux release artifacts alongside the macOS ones (even just linux-x64 initially)?
If GitHub releases are intentionally macOS-only and Linux is expected to install from source only, it would help to document that explicitly as the supported installation path.
Related search
I searched for an existing issue specifically about missing Linux binaries in GitHub releases, but only found #181, which seems to be about a different Linux/runtime/toolchain problem.
Summary
Periphery is advertised as supporting
macOS | Linux, but the GitHub release assets for the latest release are macOS-only. This breaks Linux installs for tools that consume GitHub releases directly.What I observed
For
3.7.4the latest release currently contains:periphery-3.7.4.zipperiphery-3.7.4.artifactbundle.zipAfter inspecting those assets:
periphery-3.7.4.zipcontainsperiphery,libIndexStore.dylib,LICENSE.mdfile peripheryreports a Mach-O universal binaryperiphery-3.7.4.artifactbundle.zipcontains only aperiphery-3.7.4-macos/...directorySo there doesn't seem to be any Linux release artifact right now.
Impact
In our CI we install Periphery on Ubuntu via a tool that consumes GitHub release assets. It resolves the Linux platform to:
https://github.com/peripheryapp/periphery/releases/download/3.7.4/periphery-3.7.4.zipBut that zip contains a macOS binary, so on Ubuntu it fails immediately:
/home/admin/.local/share/.../periphery: 3: Syntax error: "(" unexpectedThe problem is not Periphery's Linux support itself, but that the published release assets are macOS-only.
Request
Would you consider publishing Linux release artifacts alongside the macOS ones (even just
linux-x64initially)?If GitHub releases are intentionally macOS-only and Linux is expected to install from source only, it would help to document that explicitly as the supported installation path.
Related search
I searched for an existing issue specifically about missing Linux binaries in GitHub releases, but only found #181, which seems to be about a different Linux/runtime/toolchain problem.