Over in the Django Commons GitHub discussions @pfouque asked:
… find a way to share a test matrix so that new django version (and its supported python versions) comes automatically…
I’m not sure if and how easy it would be but it would be awesome that project get proactively tested against new versions
@Stormheg responded:
That sounds pretty rad to me!
We discussed this during a Django Commons admin meeting and we came to the conclusion there are usually other tasks associated with this as well such as updating trove classifiers in a pyproject.toml file, changelog and readme changes, removing unsupported versions from the matrix and bumping the minimum version constraints
We’d love to hear how other package maintainers tackle this, maybe there is knowledge to be shared.
The first idea that comes to my mind is to let agentic AI do this, it sounds like something it could figure out quite well on its own. Run it on a regular schedule with a prompt telling it what to do and what versions exist – to avoid it hallucinating Django 3.14 as the latest. Have it create a PR that a human can then review and merge; and boom, you’ve just cut down on one of the maintenance chores.
I probably don’t have time to experiment with that, but if someone else is reading this and is inspired: please feel free to experiment with this idea. Might make for an interesting talk topic as well…
I’m cross posting here to get more visibility and see if this is something that others have thought about or already have a solution for