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
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 https://github.com/haskell/haskell-language-server/issues/239#issuecomment-695810253.
what generates the artifacts on the release page? Is it automatic or manual?
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
@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
Most helpful comment
0.5.0 has been released