-
Notifications
You must be signed in to change notification settings - Fork 181
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
Tag a new release? #168
Comments
I'm going to make a big push on 0.7 compat tonight to get tests passing and there are a few deprecations to clean up (I have a couple changes locally). If things go smoothly, I think we should be ready for a tag tonight/tomorrow. @samoconnor, anything else you're working on or want to get in before a new tag? |
Anything else to do now that #171 has been merged? |
I'm checking out HTTP dependencies tonight and hopefully won't run into too many unrelated compat problems trying to test if we've broken anything too badly. |
ok, #175 is the last thing I want to get in before tagging, so pending good CI, I'll merge and tag. If anyone has other issues/concerns, speak now or..........wait till the next release! |
Yay! 🎉 |
There has been a lot of progress with HTTP after merging #135 and some subsequent clean up.
Several people, e.g. myself, @oxinabox, @ararslan , etc, would like a tag so we can update our packages 😊
What is left to do before that can happen?
The text was updated successfully, but these errors were encountered: