Tool information
Area for Triage: haskell
Question, Bug, or Feature?:
Feature
Virtual environments affected
Are you willing to submit a PR?
Yes
I think all package managers have the version included:
Hello @jneira,
Thank you for submitting the issue.
GHC will be automatically updated after the next image rollout most likely in the first weeks of January.
I will let you know as soon as ghc is deployed.
thanks a lot for the quick response
I think the new version should be already available via official haskell action: https://github.com/haskell/actions/tree/main/setup
It will install the new version in runtime with minor latency. As soon as image is updated, it will switch versions without latency.
@jneira maybe I missed something but I tested GitHub actions and all install methods failed for ghc-8.10.3: https://github.com/jneira/haskell-language-server/actions/runs/441063983
@jneira , it is absolutely correct code. Could you please try to rerun it? I see your last attempt was 2 days ago but, for example, new version was added to choco just yesterday. May be it is delay with updating
@maxim-lobanov hi, thanks for the tip, I've reran jobs and Windows one has been succesful but the rest continue failing https://github.com/jneira/haskell-language-server/actions/runs/441063983
Hm, looks like ghcup is not updated yet and still doesn't contain new version.
Just checked on local box:

As soon as it is updated, task will work as expected.
Unfortunately, I am not familiar with process for adding versions to ghcup so can't predict when it will be updated.
Yes, image generation uses hvr:ppa but actions/setup-haskell uses ghcup to install versions in runtime AFAIK
A pr to add support for ghc-8.10.3 was merged a two days ago: https://gitlab.haskell.org/haskell/ghcup-hs/-/merge_requests/53
It only updated yaml files, so afaiu, only the config files would be needed to make ghcup supports the new version.
setup-haskell action tries to use ghcup-1.8.0 and not sure if it takes in account the update of the yaml config.
A silly question: why not make CI do ghcup upgrade immediately after ghcup (of whatever version) is installed by the script?
@mouse07410 When image is just generated, it always has latest ghcup. But images are regenerated on weekly basis (sometimes rare because of deployment freeze) so if image was generated and deployed yesterday, and today the new version of ghcup is released, it will be outdated in CI
I think @mouse07410 want to ask why not upgrade ghcup in the setup-haskell action itself, to make it download the last version without waiting for the next image bump.
It makes more sense if the upgrade only fetches config files, and doesn't update the executable itself, like it seems.
Most helpful comment
Hello @jneira,
Thank you for submitting the issue.
GHC will be automatically updated after the next image rollout most likely in the first weeks of January.
I will let you know as soon as ghc is deployed.