-
-
Notifications
You must be signed in to change notification settings - Fork 372
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
new release #702
Comments
If we get this to pypi then I'm happy 🤩
Buky <[email protected]> schrieb am Do., 26. Dez. 2019, 18:54:
… In view of the time elapsed since the last tag, I decided to create one on
the upper major version. @jesusch <https://github.com/jesusch>, I have
just released 1.7.0
<https://github.com/jazzband/django-pipeline/releases/tag/1.7.0> which
should work with Django 3.0. Can I close this issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#702?email_source=notifications&email_token=AASA3LV3CFJPCZYMVAUB3ZDQ2TVTXA5CNFSM4I72XIB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHV5AHQ#issuecomment-569102366>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AASA3LTFZA7MQQKU3F27QTLQ2TVTXANCNFSM4I72XIBQ>
.
|
I manually released 1.7.0, while we figure out how to fix the travis build. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
last tag is from Jan 2018
there had been several commits/fixes since then
The text was updated successfully, but these errors were encountered: