Packaging/dev-tools/docs update #244

Merged
cmo merged 19 commits from packaging into master 2026-07-01 09:00:58 +00:00
Owner
No description provided.
This is arguably more standard and what a random `hatch` user would
expect. I saw no specific reasons to deviate from this standard.
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.
Reason:

```
StarletteDeprecationWarning: Using `httpx` with `starlette.testclient` is deprecated; install `httpx2` instead.
    from starlette.testclient import TestClient
```

Closes: orinoco/dump-things-server#243
chore: update project URLs, include changelog URL
All checks were successful
Test execution / Test-all (push) Successful in 1m2s
23baed424e
mih force-pushed packaging from 1521a54819
All checks were successful
Test execution / Test-all (push) Successful in 1m1s
to 018f5c45d5
All checks were successful
Test execution / Test-all (push) Successful in 59s
2026-06-30 17:47:54 +00:00
Compare
ci: make codespell workflow run on forgejo
Some checks failed
Codespell / Check for spelling errors (pull_request) Failing after 27s
Codespell / Check for spelling errors (push) Failing after 29s
Test execution / Test-all (push) Successful in 1m12s
9c6c366b40
chore: fix typo pointed out by codespell
All checks were successful
Codespell / Check for spelling errors (push) Successful in 27s
Codespell / Check for spelling errors (pull_request) Successful in 30s
Test execution / Test-all (push) Successful in 1m14s
a9f3ad5537
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
0534a14e94
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.
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 (push) Failing after 51s
Ruff / Code linting (pull_request) Failing after 53s
Test execution / Test-all (push) Successful in 1m30s
Type annotation (PR) / check (pull_request) Failing after 1m35s
7fb07f59c3
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.
mih force-pushed packaging from 7fb07f59c3
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 (push) Failing after 51s
Ruff / Code linting (pull_request) Failing after 53s
Test execution / Test-all (push) Successful in 1m30s
Type annotation (PR) / check (pull_request) Failing after 1m35s
to b9157d5de2
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
2026-06-30 18:18:47 +00:00
Compare
This fixes >100 issues. The tests continue to pass.
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
c332abbd1b
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
18f365ee1a
This commit applies a subset of the fixes that were applied
via `hatch check code --unsafe-fixes --fix`.
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
79750f4381
Ensure that an invalid token is not reported
in error messages from Forgejo-authentication
modules.
cmo merged commit e3a733d8f8 into master 2026-07-01 09:00:58 +00:00
Sign in to join this conversation.
No description provided.