Stale dependency range: barrett-land/adom-desktop-altium-bridge@^0.0.36 excludes 0.0.37

by adom

The one map of everything Adom can do with Altium Designer. Read this when the user has Altium open (or a .PcbDoc / .SchDoc / .PrjPcb / .SchLib / .PcbLib / .IntLib is present) and you need their options: drive Altium live from the cloud to add parts, read Altium libraries into KiCad, write native Altium .SchLib/.PcbLib/.IntLib, source parts with LCSC/JLCPCB tags, and publish a board as a molecule. Altium is the least-mature of the three EDA surfaces — this page is honest about what works and wha

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

Closed bug report

Adom Registry · 2mo ago ·closed by Adom Registry

A new version of barrett-land/adom-desktop-altium-bridge was published, and this package's declared dependency range on it now excludes that latest version.

Dependency: barrett-land/adom-desktop-altium-bridge
Declared range here: ^0.0.36
New latest: 0.0.37

Why this matters. A range that excludes the dependency's latest wedges update resolution. On adom-wiki CLI versions before 1.0.56, one stranded range fails the whole update sweep, so nothing in the workspace updates. On 1.0.56 and later the CLI skips just this package, so it keeps resolving to an old version and silently stops receiving updates.

How to fix it. Widen or bump the range on barrett-land/adom-desktop-altium-bridge in this package's package.json, then republish:

Set the range to admit 0.0.37, for example "barrett-land/adom-desktop-altium-bridge": "^0.0.37".
Republish with adom-wiki pkg publish.

Once you republish with a range that admits 0.0.37, this issue closes automatically.

Filed automatically by the Adom registry.

1 Reply

Adom Registry · 2mo ago

Resolved: this package now declares ^0.0.55 on barrett-land/adom-desktop-altium-bridge, which admits the current latest 0.0.55. Closed automatically by the Adom registry.