-
-
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
Release hls-1.0.0 to hackage #1470
Comments
Why do we need a |
In the last release we bumped up all packages versions to 1.0.0 and all deps bounds to 1.0.* for consistency, even if they did not change so the upload is needed |
I don't think hie-compat needs to be at 1.0, I can revert that change if necessary. |
Uploaded ghcide release candidate: https://hackage.haskell.org/package/ghcide-1.0.0.0/candidate |
@jneira Oops, it still uses |
ugh did I forget to pull last changes? sure |
@Ailrun corrected and uploaded again 🤞 |
Awesome, thanks! |
ghcide fails due to the last version of haddock-library and the lack of upper bounds for it 😟
will open a pr for master and will backport in hls-1.0.0-hackage |
Forgot to mention i did a hackage revision for ghcide-0.7.5, as it was failing for hls-plugin-api-1.0.0 and haddock-library: https://hackage.haskell.org/package/ghcide-0.7.5.0/revisions/ I assumed haddock-library was fixed in master |
|
@berberman maybe it would be handy if hls-haddock-comments-plugin could have some other hls maintainer(s). Feel free to add us, if anybody dont want to always can remove itself from the list 😄 |
@isovector #1454 (comment) should work, i hope (good move @Ailrun 😄 ) it did! #1500 |
Thanks! |
@jneira I uploaded hls-haddock-comments-plugin and added other maintainers. |
|
Uploaded |
Uploaded hls-hlint-plugin-1.0.0.1: https://hackage.haskell.org/package/hls-hlint-plugin-1.0.0.1 |
Uploaded hls-splice-plugin-1.0.0.0: https://hackage.haskell.org/package/hls-splice-plugin-1.0.0.0 |
@tittoassini hi! hls-eval-plugin is the last plugin required to upload hls itself |
Hi @jneira, I have added you as hackage maintainer of the hls-eval-plugin .
I will upload the package to hackage shortly.
Il giorno sab 6 mar 2021 alle ore 22:11 Javier Neira <
[email protected]> ha scritto:
… @tittoassini <https://github.com/tittoassini> hi! hls-eval-plugin is the
last plugin required to upload hls itself
It would be great if you could add some other hls maintainer to the list
of package maintainers, to agilize the release process 🙂
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1470 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAFRQIAE422V7VGDQF7DCLTCKLA5ANCNFSM4YMG7MOQ>
.
--
Pasqualino "Titto" Assini
http://networkpolitics.svbtle.com
http://quid2.org/
|
Hi @jneira, I have uploaded
https://hackage.haskell.org/package/hls-eval-plugin-1.0.0.0
Il giorno dom 7 mar 2021 alle ore 13:58 Pasqualino "Titto" Assini <
[email protected]> ha scritto:
… Hi @jneira, I have added you as hackage maintainer of the hls-eval-plugin
.
I will upload the package to hackage shortly.
Il giorno sab 6 mar 2021 alle ore 22:11 Javier Neira <
***@***.***> ha scritto:
> @tittoassini <https://github.com/tittoassini> hi! hls-eval-plugin is the
> last plugin required to upload hls itself
> It would be great if you could add some other hls maintainer to the list
> of package maintainers, to agilize the release process 🙂
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#1470 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAAFRQIAE422V7VGDQF7DCLTCKLA5ANCNFSM4YMG7MOQ>
> .
>
--
Pasqualino "Titto" Assini
http://networkpolitics.svbtle.com
http://quid2.org/
--
Pasqualino "Titto" Assini
http://networkpolitics.svbtle.com
http://quid2.org/
|
@tittoassini many thanks, the release is almost complete now |
...and haskell-language-server-1.0.0.0 itself has been released after fixing a problem in its cabal file with 4c80cb3 |
//cc @pepeiborra
The text was updated successfully, but these errors were encountered: