Describe the bug
We have encountered a critical breaking change regarding the linuxmusl-x64 release assets. Previously, downloading the tarball for version v1.0.70 (and other previous versions) provided a precompiled standalone binary suitable for Alpine Linux environments.
Upon investigation, we have checked all versions in the 1.0.X range and discovered that the binary is now missing across all of them. Archives that previously contained the executable have seemingly been altered retroactively, and they now extract into a package folder structure missing the standalone binary.
Because this change affects older, previously functional releases retroactively, it has broken existing deployments. Was this a deliberate architectural change to the legacy CLI packaging, or is it an unexpected regression in the release asset pipeline? Any guidance on how to obtain the musl binary moving forward would be highly appreciated.
Affected version
No response
Steps to reproduce the behavior
- Download the asset for
v1.0.70 (or any older 1.0.X release):
wget [https://github.com/github/copilot-cli/releases/download/v1.0.70/github-copilot-1.0.70-linuxmusl-x64.tgz](https://github.com/github/copilot-cli/releases/download/v1.0.70/github-copilot-1.0.70-linuxmusl-x64.tgz)
- Extract the archive:
tar -xzvf github-copilot-1.0.70-linuxmusl-x64.tgz
- Check the contents: The expected standalone binary is missing from the extracted folder structure. Repeating this for other
1.0.X tags yields the same result.
Expected behavior
Downloading and extracting github-copilot-1.0.X-linuxmusl-x64.tgz assets should yield the compiled executable binary for musl-based systems (Alpine Linux), allowing it to be executed directly in CI/CD pipelines, Docker containers, or local environments.
Additional context
- Target OS: Alpine Linux (or any
musl-based distribution)
- Affected Versions: All
1.0.X releases (e.g., v1.0.70, etc.)
Describe the bug
We have encountered a critical breaking change regarding the
linuxmusl-x64release assets. Previously, downloading the tarball for versionv1.0.70(and other previous versions) provided a precompiled standalone binary suitable for Alpine Linux environments.Upon investigation, we have checked all versions in the
1.0.Xrange and discovered that the binary is now missing across all of them. Archives that previously contained the executable have seemingly been altered retroactively, and they now extract into a package folder structure missing the standalone binary.Because this change affects older, previously functional releases retroactively, it has broken existing deployments. Was this a deliberate architectural change to the legacy CLI packaging, or is it an unexpected regression in the release asset pipeline? Any guidance on how to obtain the
muslbinary moving forward would be highly appreciated.Affected version
No response
Steps to reproduce the behavior
v1.0.70(or any older1.0.Xrelease):1.0.Xtags yields the same result.Expected behavior
Downloading and extracting
github-copilot-1.0.X-linuxmusl-x64.tgzassets should yield the compiled executable binary formusl-based systems (Alpine Linux), allowing it to be executed directly in CI/CD pipelines, Docker containers, or local environments.Additional context
musl-based distribution)1.0.Xreleases (e.g.,v1.0.70, etc.)