@mislav thanks for your reply.

After #4442 merged, if you upgrade all extensions, localExtensionUpgradeError & upToDateError won't be counted as failure since they are effectively lastest versions. However, that patch handles only when you run:

gh extension upgrade --all

but not:

gh extension upgrade some-ext

This PR follows up to update the logics for some-ext case.

if you upgrade all extensions, localExtensionUpgradeError & upToDateError won't be counted as failure since they are effectively lastest versions.

But we already don't count local extension upgrade error nor up-to-date error as failures. To demonstrate:

$ gh extension upgrade --all && echo SUCCESS
[branch]: local extensions can not be upgraded
[dependents]: already up to date
[repo-topic]: local extensions can not be upgraded
[screensaver]: already up to date
...
✓ Successfully upgraded extensions
SUCCESS

From what I can see, gh extension upgrade --all already works as I expect. What needs to change?

@mislav not if you upgrade a specific extension and thus it creates inconsistency:

$ gh extension upgrade cherry-pick
X Failed upgrading extension cherry-pick: already up to date

After this change it becomes:

$ bin/gh extension upgrade cherry-pick
already up to date
✓ Successfully upgraded extension cherry-pick

Aah, I see. So this change is about making extension upgrade <ext> (single extension) print an informative message and exit with zero status instead of printing a failure message and exiting with nonzero status?

@mislav yes.

@mislav @vilmibm any further concern?

@mislav thanks for your review and follow ups. I also thought of error handling things but failed to get a result as you did. Thanks for the insights :P