Literate AI

Repository documentation

ADR 0049: Continue installations across a declared repository move

Context

Literate AI moved from the internal NVIDIA-dev/literate-ai repository, now archived, to the public jordanhubbard/literate-ai repository. The public repository starts from a sanitized single-root snapshot; no earlier history or tags were copied.

Existing users carry the old location in three places:

Treating any two repositories as equivalent would weaken the origin check. Rewriting recorded origins would destroy provenance.

Decision

Declare repository moves explicitly in literate_ai.repository_urls. A move is a predecessor-to-successor mapping between exact GitHub coordinates. The only declaration is github.com/NVIDIA-dev/literate-ai to github.com/jordanhubbard/literate-ai.

Releases 1.0.x cannot learn the successor. For enrolled prefix installs, the 1.1.0 release publishes one bridge: the identical 1.1.0 wheel is also attached to a v1.1.0 release on the predecessor repository, which is unarchived only for that publication. 1.0.x installs then self-update once to 1.1.0, whose embedded public origin directs every later check to the successor. Pip and editable installs upgrade manually from the successor's releases.

Amended at 1.1.0 publication (2026-10-04): the bridge release was published (v1.1.0 on the predecessor, identical wheel), but it cannot complete the upgrade. The predecessor is an internal repository. 1.0.x reaches its release API with a token, then downloads the wheel from its browser_download_url, which returns 404 for non-public repositories even when authenticated. The predecessor stays internal, so 1.0.x prefix installs migrate manually by reinstalling from the successor (see the migration guide). The bridge release remains as a pointer to the successor.

Historical tags v0.1.0a1 through v1.0.1 exist in the successor as annotated tags on parentless marker commits. Each contains a README naming the release, its date and original commit, plus its changelog section. They keep version history and changelog links coherent without publishing pre-export source.

Consequences

Read the Markdown sourceConference homePublished 1.3.0 · Patch 1.3.1 in progress · Development 1.4