[tim-schilling]

References: django-commons/membership#609

Don't merge this until the repo has been transferred to the Django Commons GitHub org and the PyPI org.

I used Claude to update many of the files. This removes twine as it's no longer needed, nor used.

The release process will be:

1. Push commit with version change to GitHub
2. Tag that commit with the new version number
3. Push tag to GitHub
4. [automated] GitHub will request an approval from the admins via email (you'll also find it under the Actions tab)
5. The deployment review will be approved
6. [automated] It'll be pushed to PyPI and a draft release on GitHub will be created
7. Edit the release notes on GitHub release and publish

We can tweak this a bit to fit your needs too.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.53%. Comparing base (a567da9) to head (ffce298).

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #244   +/-   ##
=======================================
  Coverage   94.53%   94.53%           
=======================================
  Files          15       15           
  Lines         238      238           
=======================================
  Hits          225      225           
  Misses         13       13           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.