You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit aea3219
Browse filesBrowse the repository at this point in the historyBrowse files
ci: fail loud on npm publish errors that aren't EPUBLISHCONFLICT (#51)
The publish workflow used `|| true` after every `npm publish` step to
tolerate "version already published" errors during reruns. The blast
radius: every other failure mode was also silently masked, including
ENEEDAUTH cascades. This caused the v0.3.1 silent failure (2026-04-03)
and the v0.3.2 release saga (2026-04-11) - 14 publishes in a single
run failed to authenticate but all reported success.
This change replaces the unconditional tolerance with a wrapper that
exits non-zero on any failure unless the npm output matches a known
"already published" pattern (EPUBLISHCONFLICT, E409, "cannot publish
over", "already published").
Also fails loud if `bun pm pack` produces zero .tgz files, which the
previous glob-based `npm publish *.tgz` invocation would have silently
tolerated.
Closes#51
Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
0 commit comments