`ghcup upgrade --force` should refresh the cache
In #394 (closed), I was confused because neither ghcup upgrade
nor ghcup upgrade --force
upgraded ghcup to the latest version. It turns out that both commands were looking at an outdated cache file which claimed that ghcup-0.1.17
was the latest version even though ghcup-0.1.18
had just been released.
This caching behaviour makes sense for ghcup upgrade
, but since ghcup upgrade --force
is willing to spend extra time downloading and installing a binary even though that particular version is already installed, I think it should also be willing to download the latest version of that cache file.
The cache file in question was ~/.ghcup/cache/ghcup-0.0.6.yaml
.