-
-
Notifications
You must be signed in to change notification settings - Fork 210
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
Cut a new release #1050
Comments
Isn't the fix 49a89c9 contained in 8.1.0 already (as per the decoration on the commit message)? |
The fix was already released I just haven't sorted the change log as I'm very short on time and people needed the release If there's a problem on older python versions,we might need a backport |
I think it's not available in the |
please report a issue against that downstream - its not managed by us |
Thanks all. Sorry for the noise. I missed the tag detail. |
It's entirely my fault the official change log is not up2date Thanks for reaching out so we could pinpoint the missing downstream update |
I'm at PyCon sprints and there are some users eagerly awaiting the release of the fix for #1038.
Can we cut a new release? What is the process? I looked at the last release (48b1cb5), but it's not obvious to me how that's done. Presumably something like
scriv collect
, but I notice that doesn't indicate any versions to tag.Please cut a release and let me know if I can help.
The text was updated successfully, but these errors were encountered: