autokap 1.3.3 → 1.3.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/readme.md +3 -3
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "autokap",
3
- "version": "1.3.3",
3
+ "version": "1.3.4",
4
4
  "description": "AI-powered CLI tool for capturing clean screenshots of websites",
5
5
  "type": "module",
6
6
  "main": "./dist/index.js",
package/readme.md CHANGED
@@ -23,7 +23,7 @@ from the project Recapture page, store it in your CI secret manager, then call
23
23
  the webhook on deploy. CI never needs an AutoKap CLI key.
24
24
 
25
25
  ```bash
26
- BODY='{"env":"staging"}'
26
+ BODY='{}'
27
27
  SIG=$(printf '%s' "$BODY" | openssl dgst -sha256 -hmac "$AUTOKAP_WEBHOOK_SECRET" -binary | xxd -p -c 256)
28
28
  curl -X POST "https://autokap.app/api/webhooks/cloud-recapture/<project-id>" \
29
29
  -H "Content-Type: application/json" \
@@ -31,8 +31,8 @@ curl -X POST "https://autokap.app/api/webhooks/cloud-recapture/<project-id>" \
31
31
  -d "$BODY"
32
32
  ```
33
33
 
34
- Use project environments in the dashboard to map `local`, `staging`, and
35
- `production` to different base URLs without duplicating presets.
34
+ Recapture Cloud always captures the project's `prod` environment. Use the
35
+ other project environments for local debugging and staging checks.
36
36
 
37
37
  The local CLI remains available for advanced debugging:
38
38