-
Notifications
You must be signed in to change notification settings - Fork 101
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
Bump to 0.6.0 #511
Bump to 0.6.0 #511
Conversation
Not sure. I don’t think 0.5.8 was actually released yet though. |
Did you want to release a 0.5.8 from before your pull request? |
Codecov ReportBase: 87.34% // Head: 87.23% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## master #511 +/- ##
==========================================
- Coverage 87.34% 87.23% -0.12%
==========================================
Files 39 39
Lines 2316 2342 +26
==========================================
+ Hits 2023 2043 +20
- Misses 293 299 +6
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
I think that’s a good idea. What’s the mechanism for doing a release? |
There seems to be a Github action setup to do that. |
I think we're ready to move to 0.6.0 (or at least, release 0.5.8), so packages can use the fixed |
I will look at the release procedure this evening. The first target is Pypi, then conda-forge. |
I'm going to work on this tomorrow. |
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.
Changing to 0.6.0 for release
Co-authored-by: Miles Cranmer <[email protected]>
Should we be bumping to 0.6.0 or 0.6.0.dev?
cc: @MilesCranmer