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
* Upgrade git-remote-entire alongside entire
The go install path only built cmd/entire; install both binaries so it
matches the Homebrew and install.sh paths, which unpack both from the
release tarball.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Entire-Checkpoint: d95ca3cae73e
* Model release binaries as one independently-versioned set
Drive detection, gating, go-install, and verification from a single
releaseBinaries catalog instead of special-casing entire and bolting on
git-remote-entire. Each binary carries its own detected version and is
upgraded independently, so a missing or stale helper beside a current
entire is fixed on its own. Version resolution (--version then build
info) is written once in binaryVersion and shared by every binary.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Entire-Checkpoint: 391b8dd6192d
* Authenticate release check in Homebrew smoke job
The Homebrew job's Exercise step was the only upgrade step without
GITHUB_TOKEN, so entire-upgrade's release-version check hit GitHub's
API unauthenticated and 403'd on the shared runner IP's 60/hr limit.
Set GITHUB_TOKEN like the curl and go jobs already do.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Entire-Checkpoint: 9ac8d58d7318
* Reinstall when a binary's version can't be determined
A locally-built dev entire reports "dev" from --version and "(devel)"
build info, so neither source yields a version. That was a hard,
cryptic failure ("could not determine entire version from --version
output or Go build info"). Now an unreadable version is treated as
absent for any binary — anchor included — so the gate sees it as out of
date and reinstalls, with a clear note instead of an error. The error
that remains (when even reinstall can't proceed) names the binary and
reports both attempts.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Entire-Checkpoint: 8f7160ecff67
* Report every managed binary in detection and completion
Now that the upgrade manages entire and git-remote-entire independently,
print a line per binary (version + path, or "not installed"/"version
unreadable") instead of only the anchor. Same per-binary listing on
completion. Makes "already up to date" verifiable — you can see
git-remote-entire's detected version, not just entire's.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Entire-Checkpoint: 9297c7de62eb
* Column-align binary names in detection/completion output
Pad each binary name to the widest one so the version/path columns line
up across entire and git-remote-entire.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Entire-Checkpoint: 5eb342cccb6e
---------
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
returnInstallation{}, fmt.Errorf("unsupported Entire CLI installation at %s; supported update methods are Homebrew, install.sh, and go install", binaryPath)
0 commit comments