Skip to content

Decision record · ADR

ADR-0030: Aggregate workspace package assets under product releases

Status: accepted | Date: 2026-08-01

References: ADR-0008, ADR-0009, ADR-0021, RFC-0004, RFC-0006, RFC-0006:C-INTEGRATIONS

ADR-0021 correctly separated the InferLab product version from the independently owned adapter SDK and framework-integration package versions. It also selected package-scoped GitHub tags and Releases as a mirror for every wheel publication.

The 0.8.0 publication made the operator-facing cost concrete: one product release appeared alongside six package Releases even though the package index remained the canonical distribution surface and protocol version plus exact workspace locks remained the compatibility and reproduction authorities. The extra Releases fragmented one product event without adding a new trustworthy fact.

The operator confirmed that the already published 0.8.0 artifacts remain unchanged, while later product versions return to one GitHub Release per InferLab product version.

  • The adapter SDK and each integration retain independent package versions and may publish without changing the product version or unrelated packages.
  • The package index remains canonical for workspace-side wheels.
  • Exact workspace pins, Pixi locks, recorded package identity, and adapter protocol version remain the compatibility and reproduction authorities.
  • Product binaries, installer, embedded agent plugin, and LICENSE already belong to the product Release.
  • ADR-0008 keeps registry and GitHub publication operator initiated and requires verifiable artifact identity across transports.

We will retain ownership-aligned package versions while consolidating their GitHub presentation under the InferLab product Release.

The InferLab Cargo workspace, binary, embedded agent plugin, and internal Eval and Bench runners remain product-release artifacts and use the InferLab product version. The adapter SDK and each framework integration retain independent package versions and can be published without changing the product version or unrelated workspace-side packages. Adapter protocol version remains the runtime compatibility authority; exact workspace pins and Pixi locks remain the reproduction authority.

A product tag identifies the single GitHub Release for that product version. That Release presents the product binaries, installer, embedded agent plugin, LICENSE, and the exact package-index wheel plus checksum for each workspace-side distribution version selected by the tagged source snapshot. Distribution names, wheel filenames, checksums, and the Release inventory expose the independent package versions; their presence under a product tag does not imply numeric equality or establish compatibility.

A workspace-side package may still be published independently to the package index without a product version change. Such a package-only publication does not create a package-scoped GitHub tag or Release. Its canonical wheel becomes part of the next product Release’s collected workspace-side package set when the tagged source snapshot selects that version.

A protocol change remains a coordinated publication across the Rust wire contract, generated SDK, affected integrations, and product release, without requiring those artifacts to share one numeric version. Development remains checkout-based through editable path dependencies.

Existing 0.8.0 product and package tags, GitHub Releases, and registry artifacts remain historical facts and are not rewritten. The consolidated presentation begins with the next product release.

  • One product version has one operator-facing GitHub Release containing its complete distributable artifact set.
  • Independent package names and versions remain explicit without multiplying Releases.
  • PyPI, exact workspace locks, and protocol version keep their existing authority.
  • Backend-only fixes can still publish without rebuilding unchanged product artifacts or unrelated integrations.
  • Package-only publications are visible on the package index before they appear in a GitHub Release.
  • Product release preparation must resolve, collect, and checksum the exact canonical wheels selected by the tagged source snapshot.
  • Mixed package versions add release-inventory and presentation work.
  • Protocol changes still require coordinated SDK, integration, and control-plane publication.
  • Product and integration versions may differ inside one Release.
  • Qualification documentation and records continue to name exact integration package versions.
  • Existing package-scoped 0.8.0 Releases and tags remain published.
  • Cargo crates and internal measurement runners remain product-release artifacts.

Keep one package-scoped GitHub tag and Release for every workspace-side distribution version (rejected)

Section titled “Keep one package-scoped GitHub tag and Release for every workspace-side distribution version (rejected)”
  • Pros: A package publication is mirrored on GitHub immediately, Each Release contains only one distribution version
  • Cons: One product publication is scattered across several GitHub Releases and tags, Package transport details dominate the product-facing release history
  • Rejected because: The 0.8.0 publication demonstrated that package-scoped Releases fragment one operator-visible product release without adding compatibility authority beyond the package index and protocol version

Present independently versioned workspace-side wheels as assets of the InferLab product Release (accepted)

Section titled “Present independently versioned workspace-side wheels as assets of the InferLab product Release (accepted)”
  • Pros: Operators discover binaries, installer, plugin, LICENSE, wheels, and checksums in one product-version location, Wheel filenames and release inventory preserve each distribution’s independent identity and version
  • Cons: A package-only index publication is not mirrored on GitHub until the next product release, Product release preparation must collect and verify the exact canonical wheel set

Restore one lockstep version across the product and every workspace-side package (rejected)

Section titled “Restore one lockstep version across the product and every workspace-side package (rejected)”
  • Pros: A single number labels every artifact in the product Release
  • Cons: Backend-only fixes republish unchanged product and integration artifacts, Numeric equality duplicates protocol and workspace-lock compatibility authority
  • Rejected because: Release presentation does not justify coupling package version ownership that ADR-0021 correctly separated

Publish workspace-side wheels only to the package index and omit them from GitHub Releases (rejected)

Section titled “Publish workspace-side wheels only to the package index and omit them from GitHub Releases (rejected)”
  • Pros: The canonical package index remains the only wheel transport surface, Product Release preparation does not collect Python artifacts
  • Cons: The product Release no longer presents the complete distributable artifact set, Operators lose the same-byte GitHub fallback retained by ADR-0008
  • Rejected because: The operator chose one complete product Release rather than removing wheel assets from it, and ADR-0008 retains verifiable cross-transport artifact identity