-
-
Notifications
You must be signed in to change notification settings - Fork 378
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
2020-09 monthly release #449
Comments
I have nothing we need to wait for. We definitely should have a tagged release for ghcup/vscode, regardless of hackage. BTW, what generates the artifacts on the release page? Is it automatic or manual? We must not forget to add tar archives for all supported HLS versions per platform for ghcup, see #239 (comment). |
automatic with github actions triggered by the release |
Then we need to add this artifact as well |
We can/should probably automate this. I think we can create another GitHub job to run after all the build jobs are done, download the linux/macOS binaries and tar them? |
@bubba I was thinking about it, we need to get the whole process automated, there are now so many pieces to be coordinated. |
I think we should be able to use https://github.com/actions/download-artifact for this. Giving it a shot now |
See #444 (comment) |
@bubba i would mention the new implicit cradle in the release, cause it theoretically could break some setups. |
@jneira updated the release notes to mention it here https://github.com/haskell/haskell-language-server/releases/tag/0.5.0, does this seem good? |
@bubba 👍 , btw great work with the release |
0.5.0 has been released |
By our monthly cadence we should be aiming to get a release out by the weekend sometime.
What must we wait for before doing it?
I am happy to do it as a non-hackage one, it is more about getting something tagged that we are all comfortable with, given the number of downstreams that package it now
The text was updated successfully, but these errors were encountered: