pinecrew / pined-django
95%
main: 95%

LAST BUILD BRANCH: v0.1.0
DEFAULT BRANCH: main
Repo Added
Files 36
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

LAST BUILD ON BRANCH v0.1.0
branch: SELECT
CHANGE BRANCH
x

coverage: 94.783%. Remained the same
33511604326

push

github

citrux 
ci: one job per extra, at both ends of its own ranges

`uv sync --extra settings` does not install what a project asking for only
that extra would get. uv resolves the project as a whole however few extras it
then installs, so `pydantic>=2.12` from `pydantic-field` decides the version
`settings` gets too — and the `>=2.10` that extra declares was never once the
version under test. `uv pip install -e ".[settings]" --group dev` resolves that
extra and nothing else; pydantic 2.10.0 turns up, as declared.

Four jobs, `{settings, pydantic-field}` × `{lowest-direct, highest}`. The top
end is not the matrix repeated: one extra is installed, so a module reaching
across to something only the other one brings fails there rather than in the
install of whoever wanted just the one.

`tests/settings` needs a settings module of its own for this — `tests.conf`
installs the test app, whose models declare a `PydanticField`, and importing
one pulls in `json_schema_to_pydantic` from the other extra. `tests.conf_settings`
leaves the app out, and the admin tests, which assert the ordering against it,
skip themselves when it is not installed. Ninety of the ninety-six run.

`test (lowest direct)` stays as it is: everything installed, whole suite, the
bottom of every range at once.

229 of 250 branches covered (91.6%)

Branch coverage included in aggregate %.

1297 of 1360 relevant lines covered (95.37%)

0.95 hits per line

Relevant lines Covered
1360 RELEVANT LINES 1297 COVERED LINES
0.95 HITS PER LINE
Source Files on main

Recent builds

Builds Branch Commit Type Ran Committer Via Coverage
33511604326 v0.1.0 ci: one job per extra, at both ends of its own ranges `uv sync --extra settings` does not install what a project asking for only that extra would get. uv resolves the project as a whole however few extras it then installs, so `pydantic>=2.12` fro... push citrux github
94.78
33509123288 main ci: one job per extra, at both ends of its own ranges `uv sync --extra settings` does not install what a project asking for only that extra would get. uv resolves the project as a whole however few extras it then installs, so `pydantic>=2.12` fro... push citrux github
94.78
33508157692 main db: pin the fingerprint against pydantic, and measure the last two floors The hash a migration carries is taken over what `model_json_schema()` produces, so a pydantic release that renders a shape differently moves it — and every project holding ... push citrux github
94.78
33506593997 main repo: lower the pydantic floors to where they actually are The declared floors were the versions that happened to be installed, not versions anything had been run against. Bisected instead, one release at a time, running the suite at each. `pyda... push citrux github
94.78
33504784247 main ci: a cache key per job, so they stop racing for one Eight of eleven jobs reported `Unable to reserve cache … another job may be creating this cache`. `setup-uv` builds its key from the runner, the python and a hash of `cache-dependency-glob`, an... push citrux github
94.78
33504232193 main repo: retire TODO.md, the pass is done Twenty items, all fixed or answered in the five commits before this one. What was worth keeping is not in a list any more: the NULL semantics are in `AlterPydantic`'s docstring and the README, why the releas... push citrux github
94.78
33444429776 main repo: write down what a read of the source turned up Twenty items, from a pass over `src/`. Eight look like bugs: the admin reordering mutates the dict it was handed and so takes its order from whichever user loaded the page first; a `PydanticFie... push citrux github
84.88
33437857210 v0.1.0rc1 repo: drop the deprecated license classifier `license = "MIT"` already produces `License-Expression: MIT`, which PEP 639 made the canonical form and which deprecates the classifier saying the same thing. Two statements of one fact, and the wrong ... push citrux github
84.88
33437610739 main repo: drop the deprecated license classifier `license = "MIT"` already produces `License-Expression: MIT`, which PEP 639 made the canonical form and which deprecates the classifier saying the same thing. Two statements of one fact, and the wrong ... push citrux github
84.88
33437102197 main repo: take the version from the tag, not from pyproject `version` is `dynamic`, and `hatch-vcs` reads it out of git when the package is built. Nothing in the repository states a version any more, so nothing can disagree with the tag about what is... push citrux github
84.88
See All Builds (11)