Packaging/dev-tools/docs update #244
2026-07-01
fix: don't report token in error messages
Some checks failed
Codespell / Check for spelling errors (push) Successful in 44s
Codespell / Check for spelling errors (pull_request) Successful in 47s
Ruff / Code linting (pull_request) Failing after 53s
Ruff / Code linting (push) Failing after 56s
Type annotation (PR) / check (pull_request) Failing after 1m22s
Test execution / Test-all (push) Successful in 1m31s
Ensure that an invalid token is not reported in error messages from Forgejo-authentication modules.
chore: apply subset of unsafe fixes from
hatch check code
This commit applies a subset of the fixes that were applied via `hatch check code --unsafe-fixes --fix`.
2026-06-30
chore: ready for readthedocs-based doc builds
Some checks failed
Codespell / Check for spelling errors (pull_request) Successful in 40s
Codespell / Check for spelling errors (push) Successful in 43s
Ruff / Code linting (push) Failing after 50s
Ruff / Code linting (pull_request) Failing after 52s
Type annotation (PR) / check (pull_request) Failing after 1m20s
Test execution / Test-all (push) Successful in 1m30s
chore: auto-apply code formatting fixes via
hatch check fmt --fix
Some checks failed
Codespell / Check for spelling errors (push) Successful in 42s
Codespell / Check for spelling errors (pull_request) Successful in 43s
Ruff / Code linting (push) Failing after 52s
Ruff / Code linting (pull_request) Failing after 54s
Test execution / Test-all (push) Successful in 1m27s
Type annotation (PR) / check (pull_request) Failing after 1m30s
chore: auto-apply code linting fixes via
hatch check code --fix
This fixes >100 issues. The tests continue to pass.
ci: add workflow to check typing in files changed in a given PR
Some checks failed
Codespell / Check for spelling errors (push) Successful in 41s
Codespell / Check for spelling errors (pull_request) Successful in 43s
Ruff / Code linting (pull_request) Failing after 51s
Ruff / Code linting (push) Failing after 51s
Type annotation (PR) / check (pull_request) Successful in 1m20s
Test execution / Test-all (push) Successful in 1m31s
Right now, it makes no sense to type-check the entire project due to the large number of issues. This is an alternative approach that should help improve the situation over time.
ci: add code linting workflow
Some checks failed
Codespell / Check for spelling errors (push) Successful in 38s
Codespell / Check for spelling errors (pull_request) Successful in 40s
Ruff / Code linting (pull_request) Failing after 47s
Ruff / Code linting (push) Failing after 49s
Test execution / Test-all (push) Successful in 1m24s
There is a substantial number of issues reported, even with the config that was already present in `pyproject.toml`. This changeset only adds the workflow. Fixing there issues needs to be done later, possibly in an incremental fashion.
chore: add framework for Sphinx-based docs
All checks were successful
Test execution / Test-all (push) Successful in 59s
This is working towards a more structured documentation. See: orinoco/dump-things-server#214
chore: update project URLs, include changelog URL
All checks were successful
Test execution / Test-all (push) Successful in 1m2s
chore: migrate from
httpx -> httpx2 for tests
Reason:
```
StarletteDeprecationWarning: Using `httpx` with `starlette.testclient` is deprecated; install `httpx2` instead.
from starlette.testclient import TestClient
```
Closes: orinoco/dump-things-server#243
ci: remove dedicated Python installation
There should be no need for that. `uv` can manage this on its own. This has the advantage that the outcome, when run locally, is likely to be more similar than what that action might do. This may remove unexplained behavior differences between CI results and local tests.
chore: migrate from
hatch run tests:run to hatch test
This is arguably more standard and what a random `hatch` user would expect. I saw no specific reasons to deviate from this standard.