Prepare release 3.18.0 - #10015
Conversation
|
@auvipy @peterthomassen I'd like to get a release out with this fix fairly soon. Reason being is that it's slowing down 3rd party packages when they test against DRF (example). I know it's impacting Wagtail and django-allauth too. Let me know if you have any objections |
|
no problemo! just need to include all the changes in the release notes |
Sure, will get the latest changes now |
Co-authored-by: Bruno Alla <browniebroke@users.noreply.github.com>
Co-authored-by: Bruno Alla <browniebroke@users.noreply.github.com>
PR iplweb/django-pbn-client#5 zostal zmergowany (2026-08-07 07:16Z), a 0.2.3 trafilo na PyPI (08:22Z) — z `django>=5.2` zamiast dawnego capu `django<5.3` i klasyfikatorem `Framework :: Django :: 6.1`. Wraca wiec z rejestru zamiast z galezi feature'owej. Floor podniesiony do 0.2.3, bo ponizej tej wersji Django 6.1 sie nie rozwiaze. Poza porzadkiem to takze zdjecie realnego ryzyka: pin wskazywal na commit NIEZMERGOWANEJ galezi, ktora po merge'u zwykle znika — build produkcyjny przestalby sie budowac. Dodatkowo pakiet wraca do zakresu `pip-audit`, ktory pomija zaleznosci z URL-i. Zostaje jeden tymczasowy pin git: djangorestframework (3.18.0 wciaz niewydane, PR encode/django-rest-framework#10015 otwarty). Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01F134BWb3YoYPQ6zjzqoqds
how long this would take? how do you think? |
No need to chase on a daily basis, please. I'll try to find some time today (if GitHub allows) |
3 participants
This PR prepares the release of version 3.18.0.
Django 6.1 was just released: https://www.djangoproject.com/weblog/2026/aug/05/django-61-released/