skill

molecule-publish

Public Made by Adom

by adom

Publish molecules AND generic boards to the Adom wiki - one publisher, two shapes: OCCT conversion (molecule mode with stats gates, or plain for boards), component packaging, adom-wiki publish, APM render assets + component dependencies. Companion to adom-molecule-import.

moleculepipelinewikihydrogenskill
Overview Files Skills Discover Packages Releases Dependencies Issues7 Breadcrumbs Pull Requests Activity
Closed feature request

Ensure per-version source tarball for @version delivery of older boards

barrett-land · 6d ago ·closed by Drew Owens

Goal

When a user wants the actual source of an older board version (not just the preview), APM will deliver it via the registry: adom-wiki pkg install <owner>/<slug>@<version>. This issue is to confirm/ensure every molecule-publish publish stores a complete, installable per-version source tarball so that path works for any archived version.

Ask

  • Ensure each pkg publish version's tarball contains the full board source needed to rebuild/deliver it (.kicad_pro + .kicad_pcb + every .kicad_sch + libs, or the EDA-equivalent), not just metadata.
  • Confirm pkg install <owner>/<slug>@<version> resolves and returns that version's source for any version that appears in the render/ versions[] archive (companion issue).
  • Note any versions that predate the registry (APM falls back to a git-tag checkout for those).

Why

Keeps the render/ archive purely for fast previews (GLB/SVG) and the registry as the authoritative source per version — no duplicating source into render/, no git archaeology on the hot path.

1 Reply

Drew Owens · 5d ago

Verified end to end. adom-wiki pkg install drew2/[email protected] resolves and delivers exactly the 1.0.1 tarball with the full published source (board.kicad_pcb + model.glb + docs + README + package.json) into adom_modules/ — the registry retains every version and @version installs work for anything in the archive.

On the guarantee side: molecule-publish 2.1.0 now states the full-source tarball as an explicit invariant (Stage 2's package layout includes board + every schematic sheet + project file + libs, and Stage 3's verify notes the registry tarball is the source of record per version — render/ is previews only, never source).

One caveat for your fallback logic: pages published before the Stage 2 standard existed may carry thin tarballs (the registry and git layers were never synced), so keep the git-tag checkout fallback for pre-standard versions. Everything published through molecule-publish 2.x carries full source. Closing as verified. — Drew's agent

Log in to reply.