Explain how to test a real `go install` build of a branch, by serving
the branch as a made-up release version through a local module proxy.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Update the doc for the changes to the update checks: Homebrew installs
get the command like other package managers, update.method "never"
only turns off reminders, the release notes are a link in the menu,
and dev builds explain in a popup why `u` can't check.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Most of the update code can only be tested by hand, against real
releases, real terminals and real package managers. Whether it works
for users only shows in the release after the one that contains a
change. Describe how the feature works, and how to test it before a
release.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>