Files
zeekay 7d04ed8116 Refuse a publish that would ship an unresolvable range
@hanzo/event 0.3.38 reached the registry with the literal
"@hanzo/events": "catalog:" in its dependencies. Only pnpm resolves a
catalog range at pack time, so a hand-run `npm publish` shipped it
verbatim and every install answered EUNSUPPORTEDPROTOCOL. It took the
observe family with it: 0.1.9 shipped the same literal, and 0.1.10
pinned the broken build exactly, because pnpm substitutes a catalog
range with the exact version behind it.

@hanzo/ui already lost 8.0.17 and 8.0.19 to this and carried a guard
pasted into its own package.json, where it could not help anyone else.
One guard now lives in scripts/ and every publishable package runs it
from prepublishOnly, which both publishers honour.

Verified against a known-positive: npm pack writes "catalog:", pnpm pack
writes "0.2.2"; npm publish is refused, pnpm publish proceeds.

@hanzo/event 0.3.39 is published with the range resolved.
2026-09-05 14:30:53 -07:00
..