app

KiCad - the KiCad Bridge

Public Made by Adom

by adom

Reference implementation of the KiCad bridge — multi-instance Python server, forward path via kicad-cli, reverse path via in-process plugin. Most complex of the three bundled bridges.

kicadpcbschematicedabridgeabadom-bridgedesktop-app
Overview Files Skills Discover Packages Releases Dependencies Issues5 Breadcrumbs Pull Requests Activity
Closed general

Rebase retired old-wiki URLs → wiki.adom.inc

Drew Owens · 20d ago ·closed by John Lauer

Old wiki host (wiki-ufypy5dpx93o.adom.cloud, retired) still referenced:

  • CONTRIBUTING.md:21 — SDK guide link
  • page.json (readme copy) — embedded old-host link(s)
  • While here: verify release-bridge.sh's upload target (CONTRIBUTING.md:15 flow) publishes zip+manifest to wiki.adom.inc, and that the registry row's manifest URL matches.

Rebase to wiki.adom.inc. Found during an old-host dependency sweep for the factoryOS / puma-bridge work (drew2/puma-bridge).

1 Reply

John Lauer · 20d ago

Done — thanks for the sweep, this was a real find.

Both files you named, fixed:

  • CONTRIBUTING.md:21 (SDK guide link) and :15 (release flow) → wiki.adom.inc.
  • page.json readme copy → had 13 old-host links.

Two more your grep wouldn't have caught, also fixed:

  • .github/workflows/validate.yml:42 — a CI warning string pointed at the retired host.
  • CONTRIBUTING.md:17 — a stale rationale paragraph referencing the same dead script.

Repo now greps zero wiki-ufypy5dpx93o references.

On release-bridge.sh: it doesn't exist anymore. CONTRIBUTING was documenting a ship flow that had been dead for a while (tag → release-bridge.sh → upload). Rewritten to the actual current flow: version lockstep (bridge.json / BRIDGE_VERSION / manifest), then adom-wiki release create + release upload publishing the runtime zip as a Release asset.

page.json was worse than stale URLs — its embedded readme was a 10 KB snapshot from v0.8.2 claiming "23 verbs" and describing handler files (board_ops.py, schematic_ops.py) that no longer exist. It doesn't render (the page shows README.md), so it was invisible rot. Resynced from the live README, so there's one source of truth.

Your third ask — upload target + registry manifest URL — verified end to end:

Check Result
manifest version 0.9.65
manifest url https://wiki.adom.inc/download/adom/adom-desktop-kicad-bridge/0.9.65/adom-bridge-kicad-v0.9.65.zip
bridge.json updateManifestUrl https://wiki.adom.inc/api/v1/pages/.../adom-bridge-kicad-manifest.json
release zip serves HTTP 200, sha matches the manifest

All on wiki.adom.inc, no adom.cloud anywhere in the publish path.

Good luck with the factoryOS / puma-bridge work.

Log in to reply.