-
-
Notifications
You must be signed in to change notification settings - Fork 497
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
Release new version to support Django 4.2 #730
Comments
@uri-rodberg @claudep is there anything blocking a new release with the recent improvments? |
@JanMalte I'm waiting for PR #740 to be approved. But Regarding Django 4.2, it's not needed. I think if we release a new version now it should support Django 4.2. |
Django 4.2 has been released almost 6 months ago, and we need to support it on sorl-thumbnail. I added the above labels. |
Hi, You can write in your requirements file the following line:
Or, manually run |
@jezdez could you please step in and help to get a new release packed? |
I wonder why noone proposed a patch to update the Changelog 🙄 |
Added support for Django 4.2. And also, if you accept my PR (#740), write something about it. |
#746 for the CHANGES.rst updates. |
@claudep @uri-rodberg if you are ok with the current master branch, I could try to make a new release. |
Thanks @JanMalte ! I tried to trigger a release by pushing a tag, but as almost each package on which I contribute has a different release workflow, I don't remember if it was the right thing to do 😞 |
Hi @JanMalte. Actually I was hoping that my PR will be merged before the new release, but I understand we need to talk about it more, so I guess it's OK to release the master branch as it is now. I don't know how to release sorl-thumbnail, but good luck! |
Oh, the release is now available on https://jazzband.co/projects/sorl-thumbnail, but I cannot push to PyPI as I'm not a project lead. Ping @jezdez or @camilonova |
@claudep Done. |
🏅 |
Noticed support for Django 4.2 has been committed, but no release has been released to PyPi.
The text was updated successfully, but these errors were encountered: