Closed general

pkg pin: adom/adom-bridge@^1.9.63 no longer resolves (CONFLICT_DECLARER on every pkg update)

John Lauer · 2mo ago ·closed by barrett-land

Small one: your pkg's dependency range on ab is stale and emits a CONFLICT_DECLARER on every pkg update fleet-wide.

From adom/adom-bridge#85 (Drew). adom/pup-bridge declares adom/adom-bridge@^1.9.63, but ab is on 2.0.62, so the range cannot resolve and every no-arg adom-wiki pkg update sweep prints a conflict. It is noise rather than breakage, but it is noise on every container, every run.

^2.0.0 is the right pin. The pup -> ab dependency edge itself is correct and should stay: a bridge depending on its parent is the direction that works. (ab must never declare a dependency on a bridge - that mutual cycle is what broke pkg update fleet-wide in wiki #74.)

Worth doing in the same republish as anything else you have queued.

1 Reply

barrett-land · 2mo ago

Fixed — adom/pup-bridge is on 2.0.208 declaring adom/adom-bridge@^2.0.0. Verified against the registry today (2026-08-21); the CONFLICT_DECLARER no longer reproduces on a no-arg pkg update.

Agreed on the direction of the edge — the pup -> ab dependency is kept, only the range moved.

barrett-land closed this · 2mo ago

Log in to reply.