mirror of
https://github.com/kuhyx/utils.git
synced 2026-11-11 12:07:48 +01:00
Krzysztof kuhy Rudnicki
2a2f18ca56
"Are we on the newest version?" was not mechanically answerable across these repos: constraint styles had drifted per-ecosystem and a caret range is "newest-compatible" by definition, which gives a checker nothing to compare. This gate makes it answerable and then enforces the answer. Checks two things at once -- that every dependency carries an exact pin, and that the pin equals its registry's latest STABLE release -- across pub.dev, PyPI, npm, crates.io, the Go proxy, kuhyx/utils git tags, and the Flutter / Node / Python toolchains. Three deliberate design points: * Pre-releases are rejected per-ecosystem, because every ecosystem leaks them differently and each leak fails GREEN. npm lets a maintainer point `dist-tags.latest` at an rc; crates.io's `max_version` includes them; PyPI's legacy `info.version` includes yanked releases. Unit-tested with fixtures, since an end-to-end run cannot surface a wrong "up to date". * Offline, the gate serves an expired cache entry and PASSES with a DEGRADED banner (exit 3 only under --strict, which is CI). `--no-verify` is banned here, so a hook that hard-failed offline would leave no way to commit at all. * The allowlist has two entry classes. `blocked_by: transitive:<pkg>@<ver>` is a predicate that clears itself when upstream moves and must NOT carry a date; everything else is discretionary and requires `expires`, capped at 90 days. Exact pins plus latest-everywhere is provably unsatisfiable when a dependency internally constrains a shared transitive, and expiring the predicate class on a calendar would turn the gate red for a reason no commit could fix. An entry with nothing left to excuse is itself an error. One hook id, one shim, one shared implementation -- always delegating, so it cannot fork the way the 250-line cap forked into four ids, two of which were independent reimplementations. 256 tests, 100% branch coverage on every module of the gate. Also adds the workflow that runs them, which incidentally gives md_naming's 71 tests their first CI run. Not yet installed in any repo: a repo that gets the gate before its deps are bumped is instantly and permanently red, so the gate and the upgrade land together, per repo. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CRykabMwPgDzFHcARoqpaK
64 lines
1.9 KiB
Python
64 lines
1.9 KiB
Python
"""Range arithmetic. Wrong here means red for a reason no commit can fix."""
|
|
|
|
from __future__ import annotations
|
|
|
|
import pytest
|
|
|
|
from dep_freshness.constraints import _upper_for_caret, lower_bound, satisfies
|
|
|
|
|
|
@pytest.mark.parametrize("constraint,version,expected", [
|
|
("^3.12.2", "3.13.2", True),
|
|
("^3.12.2", "4.0.0", False),
|
|
("^3.12.2", "3.12.1", False),
|
|
("^0.2.1", "0.3.0", False), # caret's 0.x special case
|
|
("^0.2.1", "0.2.9", True),
|
|
("^0.0.3", "0.0.4", False),
|
|
("~1.2.0", "1.2.9", True),
|
|
("~1.2.0", "1.3.0", False),
|
|
("~>2.1.0", "2.1.5", True),
|
|
(">=3.8.0 <4.0.0", "3.13.2", True),
|
|
(">=3.8,<3.13", "3.14.7", False),
|
|
(">3.0.0", "3.0.0", False),
|
|
("<=2.0.0", "2.0.0", True),
|
|
("!=1.5.0", "1.5.0", False),
|
|
("==1.6.0", "1.6.0", True),
|
|
("1.6.0", "1.7.0", False),
|
|
("any", "9.9.9", True),
|
|
("*", "9.9.9", True),
|
|
("", "9.9.9", True),
|
|
])
|
|
def test_satisfies(constraint, version, expected):
|
|
assert satisfies(constraint, version) is expected
|
|
|
|
|
|
def test_an_unparseable_candidate_is_never_a_violation():
|
|
assert satisfies("^1.0.0", "not-a-version")
|
|
|
|
|
|
def test_a_constraint_with_no_version_at_all_admits_everything():
|
|
assert satisfies("workspace", "1.0.0")
|
|
|
|
|
|
def test_an_unparseable_bound_is_ignored_rather_than_failing():
|
|
assert satisfies(">=abc", "1.0.0")
|
|
|
|
|
|
def test_quoted_constraints_are_unwrapped():
|
|
assert satisfies('">=3.8.0 <4.0.0"', "3.13.2")
|
|
|
|
|
|
@pytest.mark.parametrize("text,expected", [
|
|
("1.2.3", "2.0.0"), ("0.2.1", "0.3.0"), ("0.0.3", "0.0.4"), ("2", "3.0.0"),
|
|
])
|
|
def test_caret_upper_bounds(text, expected):
|
|
assert _upper_for_caret(text) == expected
|
|
|
|
|
|
@pytest.mark.parametrize("constraint,expected", [
|
|
("^10.2.0", "10.2.0"), (">=1.2", "1.2"), ("==3.0.0", "3.0.0"),
|
|
("~1.4.0", "1.4.0"), ("2.0.0", "2.0.0"), ("any", None), ("", None),
|
|
])
|
|
def test_lower_bound(constraint, expected):
|
|
assert lower_bound(constraint) == expected
|