-
-
Notifications
You must be signed in to change notification settings - Fork 389
Prepare 1.6.0 release #2642
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
Prepare 1.6.0 release #2642
Conversation
jneira
commented
Jan 25, 2022
•
edited by gitpod-io
bot
Loading
edited by gitpod-io
bot
- Closes January release 1.6.0.0 #2424
I guess we probably need to bump the versions of a bunch of plugins too? |
Yeah, i was just doing that. It is enforced by the hackage workflow: it fails if the local package being tested differs from the hackage version but has the same cabal version |
Co-authored-by: J. S. <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you, always, for all your effort to cut releases. Here is one minor comment
Co-authored-by: Junyoung "Clare" Jang <[email protected]>
Co-authored-by: Michael Peyton Jones <[email protected]>
Co-authored-by: Michael Peyton Jones <[email protected]>
@pepeiborra would be this ready to go? |
Thanks @jneira for cutting a new release! |
Hi all, i firmly think that the next release must be driven by other maintainer. It will be good for the project as other maintainers than me should be able to do the relase. I hope the documentation about would be complete enough to do it. |