Skip to content

keybot: use system go for build jobs - #114

Open
chrisnojima wants to merge 1 commit into
masterfrom
local-go
Open

chrisnojima wants to merge 1 commit into
masterfrom
local-go

Conversation

@chrisnojima

Copy link
Copy Markdown
Contributor

The PATH handed to every launchd build job prepended /Users/build/code/go/bin, pinning build jobs to a hand-built go (the comment just said "need custom go to fix issue"). This drops it so jobs use the system go.

/opt/homebrew/bin also has to move ahead of /usr/local/bin. The build box has:

  • /opt/homebrew/bin/go — 1.27.1, maintained by scripts/upgrade.sh (brew upgrade go)
  • /usr/local/bin/go and /usr/local/go/bin/go — 1.23.1, a stale golang.org pkg install

Homebrew was last in the list, so simply deleting the prefix would have quietly downgraded build jobs to 1.23.1. /usr/local/bin is kept, just demoted below homebrew, since other tooling may live there.

Verified with go build ./..., go vet ./keybot/, and go test ./keybot/ ./launchd/.

Not included, but worth a follow-up: keybot/keybase.keybot.plist (the bot's own plist, installed on the box by hand) has the same ordering, and keybot/keybot.sh runs go install under it — so the keybot binary itself is currently built with 1.23.1. Alternatively, removing /usr/local/go from the box would drop the ordering trap entirely.

🤖 Generated with Claude Code

https://claude.ai/code/session_018MK1NyLj3PgQZxH343GEde

Drop the custom /Users/build/code/go/bin prefix from the PATH handed to
launchd build jobs. Homebrew's go (1.27.1) is now the one that gets used.

/opt/homebrew/bin has to move ahead of /usr/local/bin: the build box has a
stale golang.org pkg install at /usr/local/go symlinked into /usr/local/bin
(1.23.1), which would otherwise win now that the explicit prefix is gone.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018MK1NyLj3PgQZxH343GEde
@chrisnojima
chrisnojima requested a review from zoom-ua September 9, 2026 15:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants