I think we need to revert a17bdbc.
Let's say you are currently running the extended_withdeploy edition of v0.160.1, installed via Homebrew with brew install hugo. When you upgrade to v0.161.0, we will log an info messages asking you to switch to the deploy edition, which will ultimately be escalated to a warning and then to an error.
But you have no way of switching to the deploy edition when using Homebrew; they only have one recipe.
This same problem will occur with any installation method (package managers and package repositories) that doesn't currently offer two or more install commands (e.g., MacPorts, Snap, and most Linux and BSD repositories).
I think we need to revert a17bdbc.
Let's say you are currently running the
extended_withdeployedition of v0.160.1, installed via Homebrew withbrew install hugo. When you upgrade to v0.161.0, we will log an info messages asking you to switch to thedeployedition, which will ultimately be escalated to a warning and then to an error.But you have no way of switching to the deploy edition when using Homebrew; they only have one recipe.
This same problem will occur with any installation method (package managers and package repositories) that doesn't currently offer two or more install commands (e.g., MacPorts, Snap, and most Linux and BSD repositories).