feat: Inform user if cli is outdated

[prateek-who]

Check the user's version with the latest stable version to see if the user's version is outdated. Currently it only runs with the patch subcommand and the network connection has a 3 sec TTL. Any errors are silently thrown and the patching continues. Do we reduce the TTL or is this fine?

It is running on the main thread itself, but it'll block it max for 3 seconds. In case there are any issues with this implementation, please let me know. I'll make the changes

[LisoUseInAIKyrios]

3 second timeout is ok. It's only a courtesy check and not critical.

The check could run on a background thread so there is no delay before patching starts, but that will cause the console log "cli is outdated" message to appear in a non-deterministic ordering. Sometimes it will be the first line, sometimes mixed in with other patcher log statements. I think how it is now (blocks to check if outdated) is ok because in normal conditions the check will be a fraction of a second.

[cyberboh]

Is this only update CLI to latest release? How if user using Pre-release?

[LisoUseInAIKyrios]

Hmm, yeah this could use an adjustment to check pre-release versus stable.

Instead of using github api, can use github raw link to build property. This also avoid problems of non-auth github api refusing connections from some ip blocks.

Change to make:
Check if version string of the CLI contains dev, and if so then check if outdated using raw github link:
https://raw.githubusercontent.com/MorpheApp/morphe-cli/refs/heads/main/gradle.properties

If dev is not present, then fetch and check current version against:
https://raw.githubusercontent.com/MorpheApp/morphe-cli/refs/heads/dev/gradle.properties

[prateek-who]

Sure thing, do I push updates to this PR itself? Will update the github api with these raw links instead.

One small edge case: What if the latest version is the stable release, then it would never check for the dev release that happen after it right?

[LisoUseInAIKyrios]

Can make a new PR with the changes. Old merged PR's can't be reopened.

After dev merges to main, the dev branch is reset to main. So it will show a non dev release in that property file. So it still shows the latest release even if it's not a pre-release anymore.

[wchill]

FYI I got a report about the update check not working properly when on dev releases

Update available: v1.5.0 (current: v1.6.0-dev.7). Download from https://github.com/MorpheApp/morphe-cli/releases/latest

[LisoUseInAIKyrios]

Changing to GitHub raw links will fix that.

[prateek-who]

Can make a new PR with the changes. Old merged PR's can't be reopened.

After dev merges to main, the dev branch is reset to main. So it will show a non dev release in that property file. So it still shows the latest release even if it's not a pre-release anymore.

I meant:
If a user is on 1.0.8-dev.8 and stable 1.0.8 releases, they'll get a message to update to 1.0.8 since the dev branch resets to main right? But now they're on 1.0.8 (stable), so future update checks only look at the main branch. When 1.0.9-dev.1 comes out on dev, they won't be notified at all, even though they were previously tracking dev releases. What do we do here?

[LisoUseInAIKyrios]

There is no user data or anything that moves across from dev to stable update, so it can't easily remember it started at dev.

Either we tell them there is a new stable release and they can decide to change to it from dev, or if CLI is on dev and the latest is stable then the update check ignores the stable release and it will show an update again when a new dev is available.

I'm not sure which is the better approach.

[prateek-who]

Maybe we could warn the user when they are about to leave dev for stable? Something like:
"Update available: v1.0.9 (current: v1.0.9-dev.8). Note: This is a stable release. Updating will stop dev update notifications. To keep receiving dev updates, skip this and wait for the next dev release."

[LisoUseInAIKyrios]

That works. They user should know there is a new non-dev release and they can decide if they want to change to stable