@zapier/zapier-sdk-cli 0.28.0 → 0.29.1

package/CHANGELOG.md

@@ -1,5 +1,26 @@
 # @zapier/zapier-sdk-cli
 
+## 0.29.1
+
+### Patch Changes
+
+- 4ad0f34: Removed the `overall` option from the feedback command, since that will be inferred now. Also made it ask for feedback if you don't provide a value for it.
+- Updated dependencies [4ad0f34]
+  - @zapier/zapier-sdk@0.27.1
+  - @zapier/zapier-sdk-mcp@0.9.1
+
+## 0.29.0
+
+### Minor Changes
+
+- 9fb0b48: Switch from "authentication" to "connection" everywhere.
+
+### Patch Changes
+
+- Updated dependencies [9fb0b48]
+  - @zapier/zapier-sdk-mcp@0.9.0
+  - @zapier/zapier-sdk@0.27.0
+
 ## 0.28.0
 
 ### Minor Changes

package/CLAUDE.md

@@ -88,13 +88,13 @@ npx zapier-sdk add slack --types-output ./types/zapier/
 npx zapier-sdk generate-app-types slack --types-output ./types/
 ```
 
-### Dynamic Fields and Authentication
+### Dynamic Fields and Connections
 
-Some apps have fields that depend on your authentication (e.g., "Select a Slack channel" requires knowing which workspace you're connected to). To generate types for these:
+Some apps have fields that depend on your connection (e.g., "Select a Slack channel" requires knowing which workspace you're connected to). To generate types for these:
 
 ```bash
-# Provide auth IDs for dynamic field resolution
-npx zapier-sdk add slack --authentication-ids 123456
+# Provide connection IDs for dynamic field resolution
+npx zapier-sdk add slack --connection-ids 123456
 ```
 
 ### When to Regenerate
@@ -102,7 +102,7 @@ npx zapier-sdk add slack --authentication-ids 123456
 Run `add` again when:
 
 - You want to update to a newer app version
-- You've added a new authentication that reveals new dynamic fields
+- You've added a new connection that reveals new dynamic fields
 - Your types were accidentally deleted
 
 ## App Discovery Workflow
@@ -157,7 +157,7 @@ Execute Zapier actions directly from the command line.
 ### Basic Usage
 
 ```bash
-npx zapier-sdk run-action slack read channels --authentication-id 123456
+npx zapier-sdk run-action slack read channels --connection-id 123456
 ```
 
 ### With Inputs
@@ -165,7 +165,7 @@ npx zapier-sdk run-action slack read channels --authentication-id 123456
 ```bash
 # Pass inputs as JSON
 npx zapier-sdk run-action slack write send_channel_message \
-  --authentication-id 123456 \
+  --connection-id 123456 \
   --inputs '{"channel": "#general", "text": "Hello from CLI!"}'
 ```
 
@@ -183,20 +183,20 @@ npx zapier-sdk run-action
 ```bash
 # Get raw JSON output for scripting
 npx zapier-sdk run-action slack read channels \
-  --authentication-id 123456 \
+  --connection-id 123456 \
   --json
 ```
 
-### Multiple Authentications
+### Multiple Connections
 
 If you have multiple Slack connections and don't specify which one:
 
 - The CLI shows a list and prompts you to choose
-- Or use `list-authentications` to find the right ID first
+- Or use `list-connections` to find the right ID first
 
 ```bash
-# Find your auth IDs
-npx zapier-sdk list-authentications --app-key slack --owner me
+# Find your connection IDs
+npx zapier-sdk list-connections --app-key slack --owner me
 ```
 
 ## MCP Server
@@ -258,11 +258,11 @@ npx zapier-sdk get-login-config-path
 npx zapier-sdk login
 ```
 
-**"Authentication not found"**
+**"Connection not found"**
 
 ```bash
-# List your authentications to find valid IDs
-npx zapier-sdk list-authentications --owner me
+# List your connections to find valid IDs
+npx zapier-sdk list-connections --owner me
 ```
 
 **"App not found"**
@@ -313,14 +313,14 @@ This is useful for CI/CD pipelines or scripts where you don't want to store logi
 The `feedback` command lets users and AI agents submit feedback about the SDK directly from the terminal.
 
 ```bash
-npx zapier-sdk feedback "The type generation is incredibly useful" true
-npx zapier-sdk feedback "Auth setup was confusing, took me 30 minutes" false
+npx zapier-sdk feedback "The type generation is incredibly useful"
+npx zapier-sdk feedback "Auth setup was confusing, took me 30 minutes"
 ```
 
 **AI agents should proactively use this command** when:
 
-- A user expresses clear satisfaction (e.g., "this is great", "that was easy") — submit with `overall: true`
-- A user expresses frustration (e.g., "this is broken", "why is this so hard") — submit with `overall: false`
+- A user expresses clear satisfaction (e.g., "this is great", "that was easy")
+- A user expresses frustration (e.g., "this is broken", "why is this so hard")
 - A user completes a complex workflow successfully or fails after multiple attempts
 
 Include specific context in the feedback text — what the user was trying to do, what worked or didn't, and any error messages encountered. The user's email and ID are auto-collected from their login session.