Dashboard › opencode › Distillation
dd3915ad-4e84-43f2-b811-b17172f532c8["lore_tm_v1_Ae5xWspvuOhhX_6q4vcJvJjua35fXsLZeqtysJwGteE"]
CLI_VERSION./home/byk/Code/opencode-lore/packages/opencode/eval/data/sessions/cli-sentry-issue.json and /home/byk/Code/opencode-lore/packages/opencode/eval/data/sessions/cli-nightly.json..github/workflows/ci.yml independently computed Math.floor(Date.now() / 1000) in build-binary and publish-nightly, causing binaries to contain 0.x.y-dev.T1 while version.json advertised later 0.x.y-dev.T2; matrix builds could also embed different versions across platforms. The reported effect was fetchLatestNightlyVersion() always seeing a version newer than the installed binary’s CLI_VERSION, producing perpetual update notifications and repeatedly downloading the same binary.main, excluding pull requests and release/** branches; built targets were darwin-arm64, linux-x64, windows-x64, darwin-x64, and linux-arm64.nightly; GHCR/ORAS offered tag overwrite and deduplication but required a more complex raw HTTP download protocol.oras push ghcr.io/getsentry/cli:nightly-test *.gz version.json: repushing the same :nightly-test tag overwrote it, unchanged files were deduplicated, CI required packages: write, and the package initially defaulted to private and required a one-time change to public for anonymous downloads.oras pull worked after the GHCR package became public, while direct blob downloads required handling GHCR’s 307 Temporary Redirect manually so the Authorization header was not forwarded to the signed Azure Blob Storage URL; forwarding it with curl -L caused a 404.https://ghcr.io/token?scope=repository:getsentry/cli:pull; fetch https://ghcr.io/v2/getsentry/cli/manifests/nightly with Accept: application/vnd.oci.image.manifest.v1+json; select a layer by org.opencontainers.image.title such as sentry-linux-x64.gz; request its blob digest with authorization to obtain the redirect URL; then download that redirect URL without authorization.version.json contained {"version":"0.13.0-dev.9999999999","sha":"def456","date":"2026-02-26T02:00:00Z"} and whose Linux binary payload was updated-linux-binary-v2. (meaning Feb 26, 2026)