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
fix: propagate non-zero exit codes from deploy client (#989)
* fix: handle StaticSitesClient stderr and non-zero exit codes
The deploy command silently ignored failures from the StaticSitesClient
binary. When the binary crashed (e.g., missing native dependencies on
slim Docker images), the CLI reported success and exited with code 0.
This fix:
- Adds stderr handler to capture binary error output
- Adds else branch for non-zero exit codes with diagnostic message
- Calls process.exit(1) on failure so CI/CD detects it
Fixes#536, #594
Refs: ICM 21000000909499
* test: add tests for StaticSitesClient exit code and stderr handling
- stderr is captured and passed to logger.error
- Non-zero exit code triggers spinner.fail and error message
- process.exit(1) is called on binary failure
- Success path (exit code 0) remains unchanged
* fix: resolve CI type error in process.exit mock
The ReturnType<typeof vi.spyOn> didn't match the 'never' return type of
process.exit, causing tsc to fail in CI format check.
* fix: skip process.exit(1) in dry-run mode
The deploy e2e CI uses --dry-run with a dummy token, which causes
StaticSitesClient to fail with BadRequest. In dry-run mode, binary
failures should be logged but not cause process.exit(1).
Added test: 'should not call process.exit(1) in dry-run mode'
0 commit comments