Describe the bug
We’re seeing what looks like a release packaging/versioning issue across multiple releases on both macOS and Windows.
In short, downloading a CLI asset from a tagged GitHub release includes a binary that reports (and may actually be) a different, newer CLI version when run directly from a temporary directory, without touching any existing installation.
One concrete example is release v1.0.12:
- On macOS, downloading the v1.0.12 asset and running the extracted binary reports GitHub Copilot CLI 1.0.20
- A colleague reproduced the same behavior on Windows
Expected:
A binary downloaded from release tag vX.Y.Z reports X.Y.Z.
Actual:
The downloaded binary can report and include a different newer version than the release tag.
Why this matters:
This makes it hard to reliably fetch and validate a specific CLI build, and it also impacts downstream tooling and Copilot SDK scenarios that depend on a fix or certain API being present in a specific CLI version. E.g. one of our production tools using the Copilot SDK seems to broke randomly because a new version of the Copilot CLI was downloaded even if the released pointed to a previous version.
Describe the bug
We’re seeing what looks like a release packaging/versioning issue across multiple releases on both macOS and Windows.
In short, downloading a CLI asset from a tagged GitHub release includes a binary that reports (and may actually be) a different, newer CLI version when run directly from a temporary directory, without touching any existing installation.
One concrete example is release v1.0.12:
Expected:
A binary downloaded from release tag vX.Y.Z reports X.Y.Z.
Actual:
The downloaded binary can report and include a different newer version than the release tag.
Why this matters:
This makes it hard to reliably fetch and validate a specific CLI build, and it also impacts downstream tooling and Copilot SDK scenarios that depend on a fix or certain API being present in a specific CLI version. E.g. one of our production tools using the Copilot SDK seems to broke randomly because a new version of the Copilot CLI was downloaded even if the released pointed to a previous version.