djust 0.4.0 ships 30+ features focused on developer experience: flash messages, keyboard shortcuts, form recovery, scaffolding generators, debug tooling, and security hardening. Build real-time Django apps with less code than ever.

11 Apr 2026 5:00pm GMT

Introduction

Hi everyone, sorry for the late send of Issue #331.

Last week, our provider, Curated, which is owned by Buttondown, went down and wasn't able to send our newsletter for six days. You might have received it yesterday, but not everyone did. It's the first time in several years we haven't been able to land in your inbox.

We've been in touch with their support all week and appreciate your patience while this gets sorted out.

In the meantime, Will and I are looking at other provider options. If this shows up next week looking a little different, that's probably why.

If you missed it, please check out last week's Issue 331: https://django-news.com/issues/331#start

Django Newsletter

News

Django security releases issued: 6.0.4, 5.2.13, and 4.2.30

Django 4.2 has reached the end of extended support. Five CVEs (security vulnerabilities) fixed in this latest update.

djangoproject.com

DjangoCon Europe is next week!

April 15-19 in Athens, Greece. There is a Django.Social event the night before, April 14th, 6-10pm, at Ipitou The Bar, organized by Jon Gould of Foxley Talent and Andrew Miller.

djangocon.eu

Updates to Django

Today, "Updates to Django" is presented by Pradhvan from Djangonaut Space! 🚀

Last week we had 14 pull requests merged into Django by 9 different contributors - including 2 first-time contributors! Congratulations to Eddy ADEGNANDJOU and Rodrigo Vieira 🚀 for having their first commits merged into Django - welcome on board! 🥳

This week's Django highlights: 🦄

• BaseModelFormSet.get_queryset() now uses totally_ordered to ensure stable ordering by appending "pk" as a tie-breaker when the queryset lacks deterministic ordering. (#37004)
• Fixed handling of __in lookups with None in exclude() queries, ensuring correct SQL semantics by using OR and IS NULL instead of AND and IS NOT NULL. (#20024)
• Fixed setting or clearing of request.user after alogin() or alogout() when sync middleware has already populated the user. (#37017)

Django Newsletter

Django Fellow Reports

Fellow Report - Jacob

In addition to advancing work on pending security issues, reviewed some improvements around accessibility and performance. 3 tickets triaged, 16 reviewed, 12 authored, and more.

djangoproject.com

Fellow Report - Natalia

I was traveling this week so I was less available than usual. My main priority was to support Jacob with anything needed for the upcoming security release, helping keep things on track during a critical phase. I also made an effort to stay on top of inbox and notifications, though seeing my current unread count I can confirm I have failed miserably.

djangoproject.com

Sponsored Link 1

The deployment service for developers and teams.

appliku.com

Articles

Contributing to the Django community

There are a lot of ways to get involved in the Django community; this post goes in-depth to highlight all the various opportunities.

better-simple.com

Switching all of my Python packages to PyPI trusted publishing

How and why the maintainer of django-debug-toolbar and other tools is switching due to recent malicious uploads.

406.ch

A Claude Code Plugin for Triaging Django Issues

django-triage is a Claude Code plugin that searches CVEs, Trac tickets, and Django forum discussions, then scaffolds a structured triage workspace with its findings.

manfre.me

Events

Django Day Copenhagen - Call for Proposals

The third edition will be held on Friday, October 2nd 2026, a full day of talks, followed by an evening of social events.

djangoday.dk

PyOhio 2026 CFP

PyOhio will take place on Saturday & Sunday July 25-26, 2026, at the Cleveland State University Student Center in Cleveland, OH.

pretalx.com

Design Articles

Why frontends fail when you approach them like a backend

A thoughtful exploration of why frontend development is harder than most backend work, covering UX context, accessibility pitfalls, and why "just hacking together HTML and CSS" kills quality.

marijkeluttekes.dev

Sponsored Link 2

You know @login_required. Now meet @app.reasoner(). AgentField turns Python functions into production AI agents, structured output, async execution, agent discovery. Every decorator becomes a REST endpoint. Open source, Apache 2.0. Python, Go & TypeScript SDKs.

agentfield.ai

Django Job Board

Python Developer at Open Data Services

Django Newsletter

Projects

efe/django-root-secret

Django package for managing one root encryption key and decrypting encrypted secrets at runtime.

github.com

danjac/django-studio

Django project generator for rapid, opinionated full stack development.

github.com

---

This RSS feed is published on https://django-news.com/. You can also subscribe via email.

10 Apr 2026 3:00pm GMT

Switching all of my Python packages to PyPI trusted publishing

As I have teased on Mastodon, I'm switching all of my packages to PyPI trusted publishing. I have been using it to release the django-debug-toolbar a few times but never set it up myself. The process seemed tedious.

The malicious releases uploaded to PyPI two weeks ago and the blog post about digital attestations in pylock.toml finally pushed me to make the switch. All of my PyPI tokens have been revoked so there is no quick shortcut.

In the end, switching an existing project was easier than expected. I have completed the process for django-prose-editor and feincms3-cookiecontrol.

For my future benefit, here are the step by step instructions I have to follow:

0. Have a package which is buildable using e.g. uvx build

1. On PyPI add a trusted publisher in the project's publishing settings:

   • Owner: matthiask, feincms, feinheit, whatever the user or organization's name is.
   • Repository: django-prose-editor
   • Workflow name: publish.yml
   • Environment: release

2. In the GitHub repository, create a release environment in Settings / Environments. Add myself and potentially also other releasers as a required reviewer. I allow self-review and disallow administrators to bypass the protection rules.

3. Run git tag x.y.z and git push, no more uvx twine or hatch publish.

4. Approve the release in the actions tab on the repository.

5. Either enjoy or swear and repeat the steps.

I'm happy with testing the release process in production. The older I get the less I care if people think I'm stupid. That's also why feincms3-cookiecontrol 1.7.0 doesn't exist, only 1.7.1 - the process failed and I had to bump the patch version and try again. Copy the publish.yml from a known good place, for example from the django-prose-editor repository. I have added the if: github.repository == 'feincms/django-prose-editor' statement which ensures that the workflow only runs in the main repository, but that's optional if you don't care about failing workflows.

08 Apr 2026 5:00pm GMT