chore: modernize Python repo to uv + pyproject.toml

[farhan]

Important

PR implemented with the assistance of Claude Code. Refined and validated before being submitted for code review.

Modernize `django-wiki`
Part of openedx/public-engineering#506

Summary

• Package published to PyPI as openedx-django-wiki
• Replace `setup.py` with `pyproject.toml` (PEP 621 static metadata)
• Switch from pip-compile to `uv` with PEP 735 dependency groups; commit `uv.lock`
• Retain pylint as on master; add minimal `quality` tox env (repo had no prior quality tooling)
• Update CI to use `astral-sh/setup-uv`; SHA-pin all actions
• Add `python-semantic-release` + `release.yml` (OIDC trusted publishing)
• Add `commitlint.yml` to enforce conventional commit format on all future PRs to this repo
• Drop Python < 3.12 support; set `requires-python = ">=3.12"`

Removed/Updated

Deleted files: `setup.py`, `requirements/`

Removed Makefile targets:

Target	Reason
`upgrade` (pip-compile body)	Replaced by `uv lock --upgrade` + `edx_lint write_uv_constraints`

Updated Makefile targets:

Target	Change
`upgrade`	Replaced pip-compile commands with `uv lock --upgrade` and `edx_lint write_uv_constraints pyproject.toml`

Python 3.8–3.11 dropped

Python 3.8–3.11 reached end-of-life and Open edX Sumac+ dropped them platform-wide. The project already only tested Python 3.12; `requires-python = ">=3.12"` is now set explicitly.

Versioning

`setuptools-scm` with `dynamic = ["version"]` — master had a PyPI publish workflow; `python-semantic-release` controls the version string at release time via git tags.

CI / Release workflow fixes

This repo's default branch is `edx_release`, not `master`. The standard `release.yml` template ships with `branches: [master]` and two `if: github.ref_name == 'master'` guards, which meant PSR and PyPI publish would never run after merge.

Fixed in this PR:

• `release.yml`: `branches: [master]` → `branches: [edx_release]`; both `github.ref_name == 'master'` guards updated to `edx_release`
• `ci.yml`: removed the dead `push: branches: [master]` trigger. Because `release.yml` already calls `ci.yml` via `workflow_call`, keeping a separate `push:` trigger would fire CI twice on every merge to `edx_release` once the branch name was corrected — the same race-condition bug found and fixed in platform-plugin-aspects#257.

Important Notes

• This repo had no prior quality tooling (no lint/quality Makefile target, no quality tox env). A minimal `quality` tox env running `pylint --fail-under=0` was added to satisfy the org standard; pre-existing pylint findings are not blocked by this migration. Maintainers are encouraged to address these incrementally.
• `src/` layout was not adopted because the two packages (`wiki` and `django_notify`) are tightly coupled to the test project layout and the migration would require significant refactoring beyond the scope of this PR.
• The existing `commitlint.yml` workflow was retained as-is; conventional commit format is now enforced on all future PRs.
• `pypi-publish.yml` was deleted as it is superseded by the new `release.yml` (OIDC trusted publishing replaces token-based publishing).

Testing Notes

This PR has not been manually tested against the repo's own features. Testing relied on CI checks and local agent tooling (`make upgrade`, `uv run tox`, `python -m build`). Repo-owner is encouraged to run the repo's feature tests before merging.

---

🤖 Generated with Claude Code

[farhan]

Caution

release.yml targets master — auto-releases will never fire after this PR merges

This repo's default branch is edx_release. The master branch exists but has had no commits since November 2014 — all development merges into edx_release.

Why this is a breaking change: The existing pypi-publish.yml (deleted by this PR) triggered on on: release: types: [published] — a manually created GitHub Release. That flow worked regardless of branch name. This PR replaces it with PSR auto-release on push to a branch. That branch is master, which never receives commits, so PSR will never run and PyPI publishing is effectively broken from day one after merge.

As currently written, release.yml listens on branches: [master] and guards both the release and publish_to_pypi jobs with if: github.ref_name == 'master'.

Fix: Update the three occurrences in .github/workflows/release.yml:

• on.push.branches: [master] → [edx_release]
• if: github.ref_name == 'master' (×2) → 'edx_release'

@feanil -- Can you please look/share your thoughts into this issue or tag the relevant maintainer

[feanil]

That makes sense to me.