prepare 0.9.0 hackage release

[jneira]

Package Checklist:

package	@	update .cabal	upload
ghc-exactprint	@alanz	N/A	☑
hie-compat?	@wz1000	N/C	N/C
hls-plugin-api	@jneira	#1290	☑
ghcide	@pepeiborra	#1289	☑
hls-class-plugin	@Ailrun	N/C	N/C
hls-eval-plugin	@jneira	#1305	☑
hls-explicit-imports-plugin	@pepeiborra	N/C	N/C
hls-haddock-comments-plugin	@berberman	#1292	☑
hls-hlint-plugin	@jneira	#1296	☑
hls-retrie-plugin	@pepeiborra	#1288	☑
hls-splice-plugin	@konn	#1293	☑
hls-tactics-plugin	@isovector	N/C	N/C
hls		☐ (bounds)	☑

• I've linked each package with the last collaborator that uploaded it to hackage (and/or from Upload to Hackage #1175), feel free to comment or ping me if you think you should not be there. Thanks all!
• Each .cabal update should be done in a pr and cherry-picked to the 0.9.0-hackage branch (like the last time)
• Ideally we should set a lower bound over hls-plugin-api/ghcide in plugins if they need the new version to compile (so they should be bumped out first)
• The release would close this and Will 0.9.0 and future releases be uploaded to hackage? #1282

I used this for checkboxes

• ☐
• ☑
• N/C = no changes (verified via git log )

[Ailrun]

The only change in hls-class-plugin since the last release is a part of hiedb PR. It should not be released until HLS release actually includes it; that being said, there's nothing to upload for hls-class-plugin for 0.9.0

[pepeiborra]

There are no worthwhile changes in ghcide since the 0.7.2 release, other than the hiedb patch.
Or are we aiming for some kind of parity with the binary release?

[alanz]

The plan was to get ghcide out before hiedb lands, so we have a month to dogfoof hiedb before it goes into a tagged release

[pepeiborra]

We discussed that in the hiedb PR and since there had been a ghcide release recently, decided not to make another one

[jneira]

Or are we aiming for some kind of parity with the binary release?

not necessarily imo

[jneira]

@pepeiborra But hls-plugin-api has a new config field maxCompletions so it need a breaking bump, that it turns need a new lower bound in ghcide over hls-plugin-api cause it is using the new field, but it can be done with a hackage revision,

blessed transitive dependencies 😄

[pepeiborra]

Ok, in that case let's do a ghcide release as well. I'll update the changelog and then back port it to the commit before the hiedb patch

[alanz]

http://hackage.haskell.org/package/ghc-exactprint-0.6.3.4

[berberman]

hls-haddock-comments-plugin is uploaded.
Off topic: @jneira sorry to disturb you here, I didn't receive the mention because you misspelled my username...

[jneira]

oops sorry, corrected now