imccyu 70eb76eaec fix(release): keep npm's own output in the publish log ...

Retry classification needs npm's failure text, so the publish call captured its
streams instead of inheriting them. That silenced npm on the success path: the
log lost the tarball contents, the notices, and the '+ name@version'
confirmation for every package.

Pipe the streams and echo them, so the log shows what npm reported and the
caller still gets the text it classifies. The registry probe behind it keeps its
streams captured, since its JSON and its E404 are internal queries rather than
progress.

2026-08-14 16:10:06 +08:00

..

bump.ts

fix: vendor prerelease

2026-08-13 06:06:45 +08:00

families.spec.ts

fix(release): order publication by every installed dependency section

2026-08-14 16:10:06 +08:00

families.ts

fix(release): order publication by every installed dependency section

2026-08-14 16:10:06 +08:00

pack.ts

fix(release): close the review findings on the release sequences

2026-08-11 01:26:36 +08:00

process.ts

fix(release): keep npm's own output in the publish log

2026-08-14 16:10:06 +08:00

publish.ts

fix(release): keep npm's own output in the publish log

2026-08-14 16:10:06 +08:00

tarball.ts

fix(release): verify the packed install against the framework it peers on

2026-08-11 00:51:02 +08:00

verify-packed-install.ts

build(release): publish the vendored framework and the native packages publicly

2026-08-13 14:05:48 +08:00

verify.ts

fix(release): order publication by every installed dependency section

2026-08-14 16:10:06 +08:00