Note that brew upgrade leaves the old service process running - #7
Merged
Conversation
A Homebrew upgrade pours the new version into the Cellar and removes the old directory, but does not touch the running launchd process, so the service keeps serving from files that no longer exist. This turned up on a Mac today: postgresql@17 was on 17.11 on disk while the postmaster still reported 17.10. The binary on PATH is not the check, the service itself is. An AI agent wrote this text in my name. I know that is problematic. Claude-Session: https://claude.ai/code/session_01RGeqgxCgSNr26pYCnQfkhr
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
brew upgradepours the new version into the Cellar and deletes the olddirectory, but leaves the running launchd process alone. The service then keeps
serving from files that no longer exist, and nothing warns you.
Hit during a Homebrew cleanup on a Mac:
postgresql@17was 17.11 on disk whilethe postmaster still reported 17.10.
psql --versionsaid 17.11 too, so theclient on
PATHreads as proof and is not.Adds one bullet to the Service Manager section of
rules/macos.md: check theversion the service itself reports, then follow up with
brew services restart <service>.An AI agent wrote this text in my name. I know that is problematic.
https://claude.ai/code/session_01RGeqgxCgSNr26pYCnQfkhr