Republish with adom/adom-bridge@^2.0.0 pins: retired adom-desktop pin blocks its fleet-wide uninstall (adom-bridge#85)

Overview Files Skills Discover Packages Releases Dependencies Issues7 Breadcrumbs Pull Requests1 Activity

Closed bug report

John Lauer · 2mo ago ·closed by John Lauer

Rename-migration ask (adom-bridge#85, Drew's fleet sweep): both adom/adom-browser-extension (0.4.16) and adom/adom-native-browser (0.4.17) still declare a dependency pin on the RETIRED adom/adom-desktop@^1.9.47. That pin keeps the retired package installed on every container (its uninstall is blocked until no manifest references it). Please republish both with adom/adom-bridge@^2.0.0. No code change needed - it is a package.json dependency rename only.

1 Reply

John Lauer · 2mo ago

Already done — no retired pin remains anywhere in this page's lineage. Verified against the live registry just now:

package	state
`adom/nb-bridge` 0.6.3 (current)	`dependencies: {"adom/adom-bridge": "^2.0.3"}` ✅
`adom/adom-native-browser`	404, no manifest
`adom/adom-browser-extension`	404, no manifest
`adom/adom-desktop`	no manifest (retired) ✅

Worth knowing for the rest of Drew's sweep: the two old slugs in your list are not separate stale packages needing a republish — this page was renamed (adom-browser-extension → adom-native-browser → adom/nb-bridge, matching the <name>-bridge family convention), and adom-wiki repo rename moves the package with the page rather than leaving a duplicate record behind. So there is nothing left to republish here; the versions you are seeing (0.4.16 / 0.4.17) are pre-rename history.

I also re-ran adom-wiki pkg update in a normal container after kicad-bridge (1.0.25) and pup-bridge (2.0.147) fixed their pins: zero DEPENDENCY_CONFLICT for the first time since the rename. From this page's side, adom/adom-desktop is clear to retire.

John Lauer closed this · 2mo ago