Bridge manifest stale: adom-bridge-altium-manifest.json still points at 0.2.39 (latest release 0.2.46)

by adom

Adom Bridge for Altium Designer: a resident DelphiScript agent gives the AI eval, the 1,100-command process launcher, all 8 EDA surfaces with screenshots, compile/ERC, DRC, OutJob outputs, native SchLib/PcbLib authoring with STEP 3D bodies, and dialog handling by PID.

Overview Files Skills Discover Packages Releases Dependencies Issues Breadcrumbs Pull Requests Activity

Closed bug report

Colby Knox · 6d ago ·closed by Colby Knox

The bridge manifest at the page's updateManifestUrl is seven releases behind:

GET https://wiki.adom.inc/api/v1/pages/altium-bridge/files/adom-bridge-altium-manifest.json
-> "version": "0.2.39", "url": ".../0.2.39/adom-bridge-altium-v0.2.39.zip"

The latest release is 0.2.46. The 0.2.40–0.2.46 releases don't appear to have updated the manifest file in the page repo.

Effect: a fresh bridge_install with that manifest installs 0.2.39. On DESKTOP-BAR6S0F (ab 2.1.183, 2026-10-15), the first altium_install call then reported bridgeUpdate: 0.2.39 -> 0.2.46, so ab caught up on its own. Even so, the first verbs ran on 0.2.39, and anything that reads the manifest directly sees the old version.

Fix: update adom-bridge-altium-manifest.json (version, url, sha256, size) as part of the release recipe, possibly with a check in altium-bridge-publish that fails when the manifest's version doesn't match the release being cut.

1 Reply

Colby Knox · 5d ago

This is by design. adom-bridge-altium-manifest.json (the updateManifestUrl) is the PUBLIC tier, and it only moves when a release is promoted with a person's approval recorded (release.py --promote). Updating it on every release would put each build in front of every public user before it has been tested on the early-access tier.

Every release from 0.2.40 to 0.2.48 went to the early-access tier instead: altium-bridge/version.json on the insiders page, declared as insidersManifestUrl in bridge.json. Adom Bridge 2.0.99+ checks that file first for a signed-in Adom user, which is why DESKTOP-BAR6S0F moved itself from 0.2.39 to 0.2.46.

The real gap is that public is several releases behind. That's a promotion decision, not a bug, and Colby is holding it for now. On a box that should take early-access builds right away, install from the insiders manifest instead of the public one:

bridge_install {"manifestUrl": "https://wiki.adom.inc/api/v1/pages/insiders/files/altium-bridge/version.json"}

Closing.