fix(release): continue publishing plugins after failures

Merged
TH
2d ago
+172-5

Summary

Continue publishing remaining plugins after a plugin lookup or publish fails, aggregate package names and npm error codes, and withhold core when any plugin fails. Stream publish output and report signal-terminated publishes as unknown with the signal. This changes three files, including test discovery; no workflow or device behavior changes.

Fixes #4403 for release-script continuation. The npm trusted-publishing configuration problem stays open and needs a separate fix.

Validation

  • Base 45e1372fa6d8fabe26ff35ab2ec207ccc58e53bd: the new release-publish test failed because the later plugin was not attempted. At 2069d1e01c, the large-output regression failed with ENOBUFS; at 68b9eca973, the signal regression reported ENOENT instead of UNKNOWN.
  • Head 4c8e4b09ed1c15edc57a50055b83ed4f895a1770: all five focused tests passed. pnpm exec vitest run --coverage --allowOnly=false --project unit-core passed 1,980 files and 18,034 tests.
  • pnpm check:affected --run --head 4c8e4b09ed passed, receipt run-ZfHEP2, exactCommit=true.
  • GitHub checks include coverage and integration. No live publish was performed.

🤖 Generated with Claude Code