Skip to content

Commit 24e30de

Browse files
doersinoBlaisorblade
authored andcommitted
Reword message shown when binary upgrade is skipped (#3158)
This seems a bit more accurate: When the user is already running the most recent version, the message "your version is already *more* recent" is incorrect and ever so slightly confusing. The other case -- where the user is running a more recent version than is available as a binary, for which the old message is accurate -- likely occurs much less frequently.
1 parent 4ac8605 commit 24e30de

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/Stack/Upgrade.hs

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -160,7 +160,7 @@ binaryUpgrade (BinaryOpts mplatform force' mver morg mrepo) = do
160160

161161
toUpgrade <- case (force, isNewer) of
162162
(False, False) -> do
163-
$logInfo "Skipping binary upgrade, your version is already more recent"
163+
$logInfo "Skipping binary upgrade, you are already running the most recent version"
164164
return False
165165
(True, False) -> do
166166
$logInfo "Forcing binary upgrade"

0 commit comments

Comments
 (0)