The resolved `ghc-version` isn't resolved

Open

#104 opened on Dec 23, 2024 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language: TypeScript
Stars: 91
Forks: 21
PR merge metrics: No merged PRs in 30d

Description

I am writing an action which tests something against ghc latest-prerelease. There appears to be no way to get at it unless you make it the default ghc:

ghc-exe and ghc-path provide paths to the currently set ghc;, not the actual ghc installed by the setup step;
ghc-version, which claims to be the resolved ghc version, is in fact the version passed in (in my case the latest-prerelease ghcup tag).

I will try to work around this in my workflow, since I know the version of the other ghc I need, but this is somewhat annoying.

Contributor guide

No contributing guide indexed for this repository

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Research direction

Start by tracing how the action resolves the GHC requested as latest-prerelease and how it exposes ghc-version, ghc-exe, and ghc-path. Compare the resolved installed version with the requested ghcup tag; done means ghc-version reports the actual installed GHC rather than the input tag, with coverage for this case.

Written by the indexing model from the issue text.

Assessment

Tech stack: github-actions, haskell, typescript
Domain: ci-cd, devops
Issue type: Bug
Difficulty: 3/5
Estimated time: 1-2 days
Activity status: Stale
Clarity: Mostly clear
Newbie friendliness: 45/100