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.