Closed UweKeim closed 11 months ago
It was not "wrong":
At startup, Clink cannot do a network call to check for a new version -- that would introduce a noticeable delay.
Instead, Clink checks if it has an update already downloaded (in the background by a previous Clink session), and reports the version of whatever is already downloaded and ready to go.
But when applying an update, it makes a network call to make sure it gets the latest, in case there's a newer version than what is already downloaded.
So, what you experienced is possible and is intentional.
Thanks, Chris ❤️
Just started a new terminal:
I had v1.5.16 and it told me, v1.5.17 is available.
In reality, v1.5.18 is available (and was installed afterwards).
Not that this bothers me in any way, I just wanted to document it here in case this is something others recognize, too.