Rationalise uv options in workflows.

Intention is that setup/action.yaml fully configures the uv venv,
and other workflows use `--frozen` so as not to modify the venv.

Author: glenn20

.github/workflows/build.yaml

@@ -22,7 +22,7 @@ jobs:
         uses: glenn20/python-ci/setup@v1
 
       - name: Build package
-        run: uv build --frozen --no-sources
+        run: uv build
 
       - name: Store the distribution packages
         uses: actions/upload-artifact@v4

.github/workflows/check.yaml

@@ -20,10 +20,10 @@ jobs:
         uses: glenn20/python-ci/setup@v1
 
       - name: mypy
-        run: uv run --no-sources --all-extras mypy
+        run: uv run --frozen mypy
 
       - name: lint
-        run: uv run --no-sources --all-extras ruff check
+        run: uv run --frozen ruff check
 
       - name: format
-        run: uv run --no-sources --all-extras ruff format --check
+        run: uv run --frozen ruff format --check

.github/workflows/test.yaml

@@ -51,4 +51,4 @@ jobs:
           python-version: ${{ matrix.python-version }}
 
       - name: pytest
-        run: uv run --no-sources --all-extras pytest
+        run: uv run --frozen pytest

README.md

@@ -81,7 +81,7 @@ the project repo and adjust according to the project needs.
   To ensure that the `_version.py` file is updated with a new version after
   every commit or checkout, add this command to the `.git/hooks/post-commit` and
   `.git/hooks/post-checkout` files:
-  - `uv run --frozen hatch build --hooks-only > /dev/null`
+  - `uv run hatch build --hooks-only > /dev/null`
 
 ## Reusable Github Workflows provided