hookdeck-cli 1.6.1-beta.1 → 1.7.0

package/README.md

@@ -394,7 +394,7 @@ hookdeck logout
 
 When forwarding events to an HTTPS URL as the first argument to `hookdeck listen` (e.g., `https://localhost:1234/webhook`), you might encounter SSL validation errors if the destination is using a self-signed certificate.
 
-For local development scenarios, you can instruct the `listen` command to bypass this SSL certificate validation by using its `--insecure` flag. You must provide the full HTTPS URL.
+For local development scenarios, you can instruct the `listen` command to bypass this SSL certificate validation by using its `--insecure` flag. You must provide the full HTTPS URL. This flag also applies to the periodic server health checks that the CLI performs.
 
 **This is dangerous and should only be used in trusted local development environments for destinations you control.**
 
@@ -404,6 +404,14 @@ Example of skipping SSL validation for an HTTPS destination:
 hookdeck listen --insecure https://<your-ssl-url-or-url:port>/ <source-alias?> <connection-query?>
 ```
 
+### Disable health checks
+
+The CLI periodically checks if your local server is reachable and displays warnings if the connection fails. If these health checks cause issues in your environment, you can disable them with the `--no-healthcheck` flag:
+
+```sh
+hookdeck listen --no-healthcheck 3000 <source-alias?>
+```
+
 ### Version
 
 Print your CLI version and whether or not a new version is available.

package/bin/hookdeck.js

@@ -33,5 +33,5 @@ try {
 } catch (error) {
   // execFileSync will exit with the same code as the binary
   // If there's an error executing, exit with code 1
-  process.exit(error.status || 1);
+  process.exit(error.status ?? 1);
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "hookdeck-cli",
-  "version": "1.6.1-beta.1",
+  "version": "1.7.0",
   "description": "Hookdeck CLI",
   "repository": {
     "type": "git",