-
Notifications
You must be signed in to change notification settings - Fork 152
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
Releasing a new version #52
Comments
@BurntSushi, currently you are the maintainer of this package according to the hackage database. If this issue was relevant could you please change the settings to make it possible to upload a new version to hackage? |
@mmzx I can change the settings sure. But I need to enter a user account for uploading new versions. What is your Hackage account username? |
@BurntSushi it is: mmzx . |
@mmzx Thanks. I've added you. |
Brilliant, thank you! Later today I will make the necessary action(s). |
If there's a breaking change, then do a major version bump. |
Thanks! 0.2.0.0 has been uploaded to hackage. |
There are some reasons that would favor creating a new version:
base
to hackage #14 has been actually done in commit: 51b0807 .base
to hackage #14) does not let the build to succeed.What would you think about the new version to be 0.1.3.1 to make a minor version bump?
The text was updated successfully, but these errors were encountered: