Skip to content

F19.1 — How packages find each other by version

State Closed
Parent E19
Iteration Release 6
Start Date 2026-10-25
Closed Date 2026-10-25
Predecessors —
Source Owner request, 2026-10-24

Stories: 1 Closed

Story State Depends on
S19.1.1 — Decide the index and the range rule, and revise ADR-0004 Closed —

Outcome: a PEP 503 index and internal version ranges were selected on 2026-10-25 and recorded in ADR-0004.

Design

The range and bump rules are in ADR-0004. PyPI later replaced the self-hosted index (F21.5).

S19.1.1 — Decide the index and the range rule, and revise ADR-0004

State: Closed

Acceptance:

  • The owner accepts the design above, or picks PyPI (see below).
  • ADR-0004 is revised as described, with **Status:** accepted (2026-09-10), revision accepted (<date>).
  • If PyPI is chosen instead, F19.2 is Removed and replaced by a feature that publishes to PyPI from the release job.

Considered and rejected

  • Publish to PyPI. It is the simplest for consumers: no index to declare, and no confusable name. But it changes where pykit lives, needs a PyPI project per package and trusted publishing set up per package, and makes every package public on PyPI's terms. It stays the fallback if the owner prefers it, and would remove the index.
  • A hosted private index (devpi, a cloud artifact registry). It brings a server or an account to keep alive for files that GitHub already hosts.
  • GitHub Packages. It has no Python registry.
  • A flat --find-links page. uv and pip both read it, but it is not a standard index: a consumer cannot scope it to rn-forge-* the way an index entry plus first-index can.
  • Reserving the rn-forge-* names on PyPI as empty placeholders. It guards pip users, but it is a squat on a public index; the guide's advice to use uv covers the risk.