-
-
Notifications
You must be signed in to change notification settings - Fork 367
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document corresponding versions for standalone tools (e.g., fourmolu) for binary releases #2649
Comments
Related #411 |
Here's how I work around this problem: build HLS from source with extra |
I would gladly do that it it were just for myself, but I have a team of Haskell novices that I need to support as well. Matching our CI version to whatever is already distributed via ghcup would be easier than getting them all to build it themselves. This process of producing the documentation could also be useful internally for figuring out which plugins were keeping which other plugins from being built against their newest versions due to bounds on common dependencies. Trying your suggestion, it looks like (at least) |
This was easier than it sounded: a |
nice, i think you could even take ride of the |
Agreed that documenting the versions seems like a good idea. As for the specific problem here, as maintainer of the Fourmolu plugin, I've known this was coming for a while: #2254 (comment). Sorry that you've hit it. We need stylish-haskell to update to |
Exact command is:
( |
You can now get this information with |
Is your feature request related to a problem? Please describe.
I use fourmolu both via the language server and as a standalone tool in my CI process. When the versions differ, sometimes the behavior does too, which results in the CI checks failing even though everything looks OK according to the language server. This was especially surprising with today's 1.6.0.0 release, which I had expected would be built against fourmolu 0.5.0.1. (Whatever version is included in the language server differs in its behavior with respect to Haddock comments with
comma-style: leading
.)Describe the solution you'd like
Document which versions of the standalone tools correspond to the plugins in the released haskell-language-server binaries, so that I can pin my standalone tool installs to those versions.
Describe alternatives you've considered
I can't just go by the bounds listed in the cabal file for the plugin because they admit multiple major versions. The versions listed in the various nix files differ, so I can't go by those either.
The text was updated successfully, but these errors were encountered: