Skip to content

[Draft] Release 3.3 #125

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

Draft
wants to merge 16 commits into
base: master
Choose a base branch
from
Draft

[Draft] Release 3.3 #125

wants to merge 16 commits into from

Conversation

miggol
Copy link
Contributor

@miggol miggol commented Jul 1, 2025

This is a compatibility release aiming to support Django 5.1. It also contains some bugfixes.

To do:

  • Merge open PRs into develop
  • Evaluate if Django 5.2 support can be easily included
  • Update CI test workflows
  • Write release notes
  • Update version in pyproject.toml

Leaving this as a draft until the above is addressed. Scheduled to merge ~July 18th.

bbonf and others added 14 commits August 5, 2024 13:35
Previously, the code for detecting 'safe' strings was completely broken to the point of 'how did I write this'. This implements the intended behaviour correctly
…rability-transformat

fix: fixed an XSS exploit in transformat
This provides compatiblity with Django 5.1. The hidden attribute is available from Django 4.0 and up with the same semantics as `is_hidden`. (In fact, it used to call `is_hidden`).
…-python-312

Avoid deprecated escaping for Python 3.12
…el-for

prevent assigning empty for="" attributes to <label>s
@tymees
Copy link
Member

tymees commented Jul 1, 2025

One of the issues (the one that crashes tests) is the CSP + SAML integration problem; if you want, I'm willing to fix that up. (Seeing as I still do SAML support)

@miggol
Copy link
Contributor Author

miggol commented Jul 9, 2025

One of the issues (the one that crashes tests) is the CSP + SAML integration problem; if you want, I'm willing to fix that up. (Seeing as I still do SAML support)

That would be awesome, Ty!

@miggol
Copy link
Contributor Author

miggol commented Jul 18, 2025

There is a single small issue (#127) blocking 5.2 support, at least as far as the Django tests are concerned. I'm calling that DSC 3.3 will support 5.1 and we can support 5.2 pretty shortly afterwards in 3.4.

…ngo-51

Fixes required for Django 5.1 support
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants