Update release documentation, workflow and build-and-check job to uv (#2846)

Update release documentation, workflow and build-and-check test to `uv`

Aligns `django-stubs` with the changes I have been making in `djangorestframework-stubs`.

Author: intgr

.github/workflows/release.yml

@@ -41,16 +41,14 @@ jobs:
     permissions:
       id-token: write
     steps:
-      - name: Setup python to build package
-        uses: actions/setup-python@v6
+      - name: Install uv & Python
+        uses: astral-sh/setup-uv@v6
         with:
-          python-version: '3.12'
-      - name: Install build
-        run: python -m pip install build
+          python-version: "3.13"
       - uses: actions/checkout@v5
         with:
           fetch-depth: 0
       - name: Build package
-        run: python -m build
+        run: uv build
       - name: Publish to PyPI
         uses: pypa/[email protected]

.github/workflows/test.yml

@@ -172,16 +172,17 @@ jobs:
       - uses: actions/checkout@v5
         with:
           fetch-tags: true
-      - uses: actions/setup-python@v6
+      - name: Install uv & Python
+        uses: astral-sh/setup-uv@v6
         with:
-          python-version: '3.12'
-      - name: Install dependencies
-        run: python3 -m pip install --upgrade build twine
+          python-version: "3.13"
+      - name: Ensure uv.lock is up to date
+        run: env --unset=UV_FROZEN uv lock --check
       - name: Build
         run: |
-          python3 -m build .
-          python3 -m build ext/
+          uv build .
+          uv build ext/
       - name: Check package metadata
         run: |
-          twine check --strict dist/*
-          twine check --strict ext/dist/*
+          uvx twine check --strict dist/*
+          uvx twine check --strict ext/dist/*

CONTRIBUTING.md

@@ -116,7 +116,7 @@ This rule helps us avoid tying in too closely to Django’s undocumented interna
 
 ## Releasing `django-stubs`
 
-1. Open a pull request that updates `setup.py`, `ext/setup.py` and `README.md`
+1. Open a pull request that updates `pyproject.toml`, `ext/pyproject.toml` and `README.md`
    (anyone can open this PR, not just maintainers):
 
     - Version number `major.minor.patch` is formed as follows:
@@ -125,11 +125,12 @@ This rule helps us avoid tying in too closely to Django’s undocumented interna
 
       `patch` is sequentially increasing for each stubs release. Reset to `0` if `major.minor` was updated.
 
-    - Update the `version=` value within `setup(...)` call in **both** `setup.py` files. The versions must be in sync.
-    - Update `django-stubs-ext>=` dependency in root `setup.py` to the same version number.
+    - Update the `version =` value within `[project]` section in **both** `pyproject.toml` files. The versions must be in sync.
+    - Update `django-stubs-ext>=` dependency in root `pyproject.toml` to the same version number.
+    - Update lockfile, run: `uv lock`
     - Add a new row at the top of ['Version compatibility' table in README.md](README.md#version-compatibility).
     - Use pull request title "Version x.y.z release" by convention.
-    - Add the correct classifiers to `setup.py` if support is added for a new Python or Django version
+    - Add the correct classifiers to `classifiers =` if support is added for a new Python or Django version
 
 2. Ensure the CI succeeds. A maintainer must merge this PR. If it's just a version bump, no need
    to wait for a second maintainer's approval.