Repository navigation
Conversation
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
The declared range is `httpx==0.28.*` and `pytest==9.*`, but the matrix only installs the newest of each, so the bottom of the range is never exercised. This adds one matrix entry, on Python 3.11, that pins both to the floor of the declared range before installing: it reuses the job's steps instead of copying them into a second job. `httpx 0.28.0` + `pytest 9.0.0` on Python 3.11.17: 354 passed, coverage 100.00% (the configured floor), so the leg is green on the current tree.
efdfc9d to
7c3c0c7
Compare
|
|
On the quality gate: the failing condition is 28.4 % Duplication on New Code, on a PR whose new code is seven lines of CI YAML — one matrix There is nothing to factor out here: the alternative I tried first was a separate job with its own So I would rather not contort the workflow to satisfy that metric. If you want the gate clean instead, the two options are to exclude |
|
Hi, can you target develop please? |
|
Retargeted to |
The declared range is
httpx==0.28.*andpytest==9.*, but the matrix only ever installs the newest of each, so the bottom of the range is never exercised. This adds a leg that installshttpx==0.28.0andpytest==9.0.0on Python 3.11 and runs the suite there.It changes no dependency and closes nothing by itself: it is the measurement that a
>=range (#201) needs before it can be defended, since today nobody knows whether 0.28.0 or 9.0.0 still work. When the declared ranges move, the two pins in this job move with them — if they drift outside the range, the job fails onResolutionImpossiblerather than passing quietly.httpx 0.28.0+pytest 9.0.0on Python 3.11.17: 354 passed, coverage 100.00% (the configured floor).Part of #201.