Four repos run the dependency-floor gate under a name the standard does not use. §7's job table
names it floors:
| Job |
What it does |
floors |
every direct dependency resolved at its declared floor, wheel-only, on every matrix entry, then the suite or an import |
Current state across the 22 repos that carry the gate:
| repo |
job name |
| 18 repos |
floors |
faststream-concurrent-aiokafka |
lowest |
faststream-outbox |
lowest |
modern-di-faststream |
lowest |
lite-bootstrap |
lowest-direct |
The four predate the standard: they are where the idea was worked out, and #107 itself proposed the
name lowest. The standard then landed with floors in #109. So this is drift
by sequence, not by disagreement, and the table and the repos simply have not been reconciled.
Why it is worth reconciling rather than leaving
The names are how anything cross-repo addresses the job. An agent or a script asked to check
whether a repo gates its floors reads _checks.yml and looks for the row the standard names. Three
spellings means every such check needs a synonym list, and a repo that adds a fifth spelling is
indistinguishable from one that has no gate at all. §7 also closes with "Drift that nobody recorded
is not an exemption", and none of these four has a row.
lowest is also the less accurate name: it describes the resolution strategy passed to uv, not
what the job establishes. lowest-direct names the flag outright.
Cost
Renaming is free right now. No repo in the org has a required status check: all 24 return
404 Branch not protected, and lite-bootstrap's ruleset on main has an empty rules array. So
no rename can break a merge gate, and no branch protection needs updating first. That will stop
being true the moment anyone turns protection on, which is an argument for doing it now rather than
later.
Decision needed
Three of the four are yours, so this is your call rather than something to sweep:
- Rename all four to
floors. One line per repo. My recommendation.
- Amend §7 to permit
lowest as an alias. Cheaper to write, but it keeps two spellings alive
permanently and the table stops being a name anything can rely on.
- Grant the four an exemption row. Records the drift honestly, changes nothing, and leaves the
cross-repo addressing problem in place.
Happy to do (1) as four one-line PRs if you want it.
Related
Four repos run the dependency-floor gate under a name the standard does not use. §7's job table
names it
floors:floorsCurrent state across the 22 repos that carry the gate:
floorsfaststream-concurrent-aiokafkalowestfaststream-outboxlowestmodern-di-faststreamlowestlite-bootstraplowest-directThe four predate the standard: they are where the idea was worked out, and #107 itself proposed the
name
lowest. The standard then landed withfloorsin #109. So this is driftby sequence, not by disagreement, and the table and the repos simply have not been reconciled.
Why it is worth reconciling rather than leaving
The names are how anything cross-repo addresses the job. An agent or a script asked to check
whether a repo gates its floors reads
_checks.ymland looks for the row the standard names. Threespellings means every such check needs a synonym list, and a repo that adds a fifth spelling is
indistinguishable from one that has no gate at all. §7 also closes with "Drift that nobody recorded
is not an exemption", and none of these four has a row.
lowestis also the less accurate name: it describes the resolution strategy passed to uv, notwhat the job establishes.
lowest-directnames the flag outright.Cost
Renaming is free right now. No repo in the org has a required status check: all 24 return
404 Branch not protected, andlite-bootstrap's ruleset onmainhas an emptyrulesarray. Sono rename can break a merge gate, and no branch protection needs updating first. That will stop
being true the moment anyone turns protection on, which is an argument for doing it now rather than
later.
Decision needed
Three of the four are yours, so this is your call rather than something to sweep:
floors. One line per repo. My recommendation.lowestas an alias. Cheaper to write, but it keeps two spellings alivepermanently and the table stops being a name anything can rely on.
cross-repo addressing problem in place.
Happy to do (1) as four one-line PRs if you want it.
Related
lowestfloors