lerd update checks, confirms, installs and refreshes the framework definitions the sites use, then stops without a word about what actually changed. doctor and status both end by telling the user to run lerd whatsnew, so the two commands that did not update anything advertise the changelog while the one that just did says nothing.
After a successful update it should show the same summary lerd whatsnew prints for the versions it moved across. A package managed install is deferred to apt, dnf or brew and never reaches that point, so this only covers the self managed path, and an unattended run wants it suppressed rather than dumped into a log.
lerd update checks, confirms, installs and refreshes the framework definitions the sites use, then stops without a word about what actually changed. doctor and status both end by telling the user to run lerd whatsnew, so the two commands that did not update anything advertise the changelog while the one that just did says nothing.
After a successful update it should show the same summary lerd whatsnew prints for the versions it moved across. A package managed install is deferred to apt, dnf or brew and never reaches that point, so this only covers the self managed path, and an unattended run wants it suppressed rather than dumped into a log.