Skip to content

E19 — Version ranges between packages

State Closed
Start Date 2026-10-25
Closed Date 2026-10-25
Feature State Iteration Stories
F19.1 — How packages find each other by version Closed release-6 1 Closed
F19.2 — The package index Closed release-6 2 Closed
F19.3 — Internal requirements become ranges Closed release-6 2 Closed

Each rn-forge-* package pins every other one it needs by one git tag URL (ADR-0004). A URL admits exactly one version, and uv refuses two URLs for one distribution. As a result:

  • every additive commons release forces a patch release of each package that depends on commons, only to move a pin (E18's commons 0.7.0 alone would re-tag seven packages for that reason, which is why F18.5 folded into F19.3);
  • a consumer that takes two packages at different times cannot install them together until both are re-tagged on the same commons.

This epic lets packages depend on each other by version range. pykit publishes a standard package index of its existing release files, and each internal requirement becomes a range that admits every compatible release. The coordinated release that switches every package to ranges is the last one that has to re-tag dependents for a pin.

Back to the work index

Context

What ranges fix, and what they don't. With ranges, an additive release (a patch before 1.0, a minor after) needs no release of its dependents. A consumer simply locks the newest version every range admits. A breaking release still needs each dependent to widen its upper bound, after checking that it works on the new version. That is real work and should stay a release.

Outcome. The range check and the index publish live in files pykit owns, and the Release 6 cut moved every package to ranges. The self-hosted index was later retired for PyPI (E21); consumer usage is in the consuming guide.

Considered and rejected

  • Exact pins, re-tagging every dependent on each release. That is today's rule. It costs six releases for one additive commons change, and still breaks a consumer that takes packages at different times.
  • One version for the whole workspace. ADR-0004 already rejected it: it couples packages whose dependencies and release needs differ.
  • Loosening only the git pins (a branch instead of a tag). A branch moves under a consumer's feet, which is why ADR-0004 ended the feature/upgrade interim.