mirror of
https://github.com/kuhyx/utils.git
synced 2026-11-11 16:14:07 +01:00
"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
52 lines
1.7 KiB
Python
52 lines
1.7 KiB
Python
"""`Cargo.toml` -> crates.io dependencies.
|
|
|
|
A dependency is either a bare string (`serde = "1.0.229"`) or a table with a
|
|
`version` key; path and git dependencies have no registry version and are
|
|
skipped. Cargo's bare `"1.0"` is a caret range, so only a full three-part
|
|
version counts as pinned — `"1.0"` is reported unpinned, which is correct.
|
|
"""
|
|
|
|
from __future__ import annotations
|
|
|
|
from pathlib import Path
|
|
import tomllib
|
|
|
|
from dep_freshness._tables import CARGO
|
|
from dep_freshness.models import Dep
|
|
from dep_freshness.parsers._lines import index
|
|
from dep_freshness.versions import exact_pin
|
|
|
|
_SECTIONS = (
|
|
("dependencies", False),
|
|
("dev-dependencies", True),
|
|
("build-dependencies", True),
|
|
)
|
|
|
|
|
|
def parse(path: Path) -> list[Dep]:
|
|
try:
|
|
data = tomllib.loads(path.read_text(encoding="utf-8"))
|
|
except (OSError, tomllib.TOMLDecodeError):
|
|
return []
|
|
lines = index(path)
|
|
deps: list[Dep] = []
|
|
for section, is_dev in _SECTIONS:
|
|
for name, spec in (data.get(section) or {}).items():
|
|
if isinstance(spec, dict):
|
|
if "path" in spec or "git" in spec:
|
|
continue
|
|
constraint = str(spec.get("version") or "")
|
|
else:
|
|
constraint = str(spec)
|
|
if not constraint:
|
|
continue
|
|
pinned = exact_pin(constraint)
|
|
if pinned and pinned.count(".") < 2:
|
|
pinned = None # "1.0" is a caret range in Cargo, not a pin
|
|
deps.append(Dep(
|
|
ecosystem=CARGO, name=str(name), constraint=constraint,
|
|
path=path, line=lines.get(str(name), 0), pinned=pinned,
|
|
dev=is_dev,
|
|
))
|
|
return deps
|