Stale dependency range: adom/adom-basic-parts@^0.2.0 excludes 0.3.0

by adom

The one map of everything Adom can do with Fusion 360 (Electronics). Read this when the user has Fusion open (or a .f3d / .f3z / .fbrd / .fsch / .lbr is present) and you need their options: drive Fusion live from the cloud, connect to Autodesk cloud designs, update board libraries preserving silk, export to Hydrogen / JLCPCB / STEP, source parts and drop-in .lbr libraries, and publish a board as a molecule. Each surface links to its canonical tool.

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 adom/adom-basic-parts was published, and this package's declared dependency range on it now excludes that latest version.

Dependency: adom/adom-basic-parts
Declared range here: ^0.2.0
New latest: 0.3.0

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 adom/adom-basic-parts in this package's package.json, then republish:

Set the range to admit 0.3.0, for example "adom/adom-basic-parts": "^0.3.0".
Republish with adom-wiki pkg publish.

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

Filed automatically by the Adom registry.

1 Reply

Adom Registry · 2mo ago

Resolved: this package now declares ^0.3.4 on adom/adom-basic-parts, which admits the current latest 0.3.4. Closed automatically by the Adom registry.