chore: remove stale committed binaries (theta-agent, theta-agent-linux-amd64)
These were never used by theta-agent itself -- only by theta-suite's setup.sh, which installed the committed theta-agent-linux-amd64 directly instead of downloading a current release binary (this repo's own install.sh has always downloaded from GitHub Releases instead). A stale committed binary has caused this exact class of bug at least twice before (see the v1.5.0 CHANGELOG entry: an old committed binary predating join-key support meant a fix in this repo never reached hosts installed via setup.sh) -- most recently, an installed agent whose `update` command 404'd against a dead SSO /resources/ URL that self-update moved away from months ago, because the binary setup.sh had installed predated that fix entirely. theta-suite's setup.sh is being changed in the same pass to download https://github.com/theta42/theta-agent/releases/latest/download/theta-agent-linux-amd64 instead, matching this repo's own install.sh and permanently closing this bug class rather than just fixing today's instance of it. Both files were already .gitignore'd (theta-agent, theta-agent-*) -- they'd been force-added at some point, bypassing that.
This commit is contained in:
BIN
Binary file not shown.
Binary file not shown.
Reference in New Issue
Block a user