Unreleased
v3.2.0-17
Other Notes
The patch diff color palette was modified to make it more accessible for all users, including those with common color deficiencies.
v3.2.0
Prelude
This release is another smaller release that focuses on bumping the supported dependencies and updates the test matrix in advance of future, larger changes. As always, recent versions of Python (3.12, 3.13) and Django (5.0, 5.1) are now supported, while support for older Python (3.7, 3.8) and Django (3.2, 4.0, 4.1) versions has been removed. More information is included below.
New Features
The version of Django used is now checked on start-up. This can help avoid issues where deployers forget to update their Django version and see odd behavior as a result.
Django 4.2 is now supported.
Django 5.0 is now supported.
Django 5.1 is now supported.
The sample
pwclientrc
files found at/project/<project>/pwclientrc
will now use therest
backend by default if the REST API is enabled. In addition, it is now possible to download a samplepwclientrc
file even if the XML-RPC API backend is disabled.
Python 3.12 is now supported.
Python 3.13 is now supported.
Upgrade Notes
Django 4.0 is no longer supported. It is no longer supported upstream and most distributions provide a newer version.
Django 3.2 and 4.1 are no longer supported. Bother releases are no longer supported upstream and most distributions provide a newer version.
Python 3.8 is no longer supported. It is no longer supported upstream and most distributions provide a newer version.
Python 3.7 is no longer supported. It is no longer supported upstream and most distributions provide a newer version.
Bug Fixes
Message IDs containing slashes will now have these slashes percent-encoded. Previously, attempts to access submissions whose Message IDs contained slashes would result in a HTTP 404 on some Django versions. If you wish to access such a submission, you must now percent-encode the slashes first. For example, to access a patch, cover letter or comment with the following message ID:
You should now use:
Both the web UI and REST API have been updated to generate URLs in this format so this should only be noticable to users manually generating such URLs.
Fix an issue whereby comment-based events would cause a HTTP 500 error for the events API (
/api/events
).