managed-deepagents 0.10.1-dev.4 → 0.10.1-dev.6

package/README.md

@@ -388,6 +388,17 @@ exact issuer and fetches its public `/.well-known/jwks.json`; it does not trust
 an issuer supplied by an incoming token. LangSmith must have signing keys
 configured, and the agent must be able to reach that public-key endpoint.
 
+### Setting up channels on deploy
+
+`mda deploy` sets up the agent's Slack, GitHub and Linear channels. A channel
+already set up on the deployment is set up again before the new revision is
+uploaded, so a setup that fails stops the deploy before anything changes. A new
+channel, and every channel on a first deploy, is set up once the new revision
+is live. A deploy that sets up a new channel, such as the first one, can't use
+`--no-wait`; once the channels are set up, later deploys can. To check the
+channels, or finish setting them up, without deploying, run
+`mda channels setup`.
+
 ## Tool and middleware runtime types
 
 Use `ManagedToolRuntime<State, Context>` for tools and tool-call hooks. Use
@@ -707,17 +718,17 @@ LangSmith creates a managed app in the workspace you already authorized it in,
 and says so. When you haven't authorized it yet, or on self-hosted LangSmith,
 deploy stops before uploading and says what to set.
 
-When Slack still needs you once the deployment is live, to authorize LangSmith
+When Slack still needs you during setup, to authorize LangSmith
 or to install the new app (some workspaces have an admin approve it first),
 deploy prints the link and waits, continuing as soon as Slack reports it done.
 In a terminal the link also opens in your browser, and Ctrl-C skips the
 channel. Without one, deploy waits up to an hour, so a coding agent running it
 can hand you the link; Ctrl-C stops it.
 
-If a setup step fails once the deployment is live, deploy offers to try again
-or to continue without the Slack channel. Without a terminal the failure ends
-the deploy, once the other channels are set up. An agent with a Slack channel
-can't be deployed with `--no-wait`, because setup needs the live deployment.
+If a setup step fails, deploy offers to try again or to continue without the
+Slack channel. Without a terminal the failure ends the deploy, once the other
+channels are set up. See [Setting up channels on deploy](#setting-up-channels-on-deploy)
+for when deploy sets the channel up.
 
 ## GitHub channels
 
@@ -990,10 +1001,10 @@ person to open and waits up to an hour for them to finish. `GH_WEBHOOK_SECRET`
 and `GH_APP_BOT_ID` (the App bot account's numeric user ID) are different: the
 deployment reads them, and they override what Agent Auth stores.
 
-If a setup step fails once the deployment is live, deploy offers to try again
-or to continue without the GitHub channel. Without a terminal the failure ends
-the deploy, once the other channels are set up. An agent with a GitHub channel
-can't be deployed with `--no-wait`, because setup needs the live deployment.
+If a setup step fails, deploy offers to try again or to continue without the
+GitHub channel. Without a terminal the failure ends the deploy, once the other
+channels are set up. See [Setting up channels on deploy](#setting-up-channels-on-deploy)
+for when deploy sets the channel up.
 
 ## Linear channels
 
@@ -1119,10 +1130,10 @@ without one it prints them before the install link for an admin to open.
 Without the redirect URI, Linear answers the install with "Invalid
 redirect_uri".
 
-If a setup step fails once the deployment is live, deploy offers to try again
-or to continue without the Linear channel. Without a terminal the failure ends
-the deploy, once the other channels are set up. An agent with a Linear channel
-can't be deployed with `--no-wait`, because setup needs the live deployment.
+If a setup step fails, deploy offers to try again or to continue without the
+Linear channel. Without a terminal the failure ends the deploy, once the other
+channels are set up. See [Setting up channels on deploy](#setting-up-channels-on-deploy)
+for when deploy sets the channel up.
 `mda delete` removes the credentials; delete the app itself in Linear.
 Deployments set up by an earlier `mda` keep the app as workspace connections,
 which only a LangSmith workspace admin can delete.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "managed-deepagents",
-  "version": "0.10.1-dev.4",
+  "version": "0.10.1-dev.6",
   "description": "Managed Deep Agents — the `defineDeepAgent` authoring interface plus the CLI that compiles and deploys a code-first Deep Agent repository to a managed LangGraph runtime.",
   "keywords": [
     "langchain",
@@ -66,12 +66,12 @@
     "zod": "^4.6.2"
   },
   "optionalDependencies": {
-    "@langchain/managed-deepagents-darwin-arm64": "0.10.1-dev.4",
-    "@langchain/managed-deepagents-darwin-x64": "0.10.1-dev.4",
-    "@langchain/managed-deepagents-linux-arm64": "0.10.1-dev.4",
-    "@langchain/managed-deepagents-linux-x64": "0.10.1-dev.4",
-    "@langchain/managed-deepagents-win32-arm64": "0.10.1-dev.4",
-    "@langchain/managed-deepagents-win32-x64": "0.10.1-dev.4"
+    "@langchain/managed-deepagents-darwin-arm64": "0.10.1-dev.6",
+    "@langchain/managed-deepagents-darwin-x64": "0.10.1-dev.6",
+    "@langchain/managed-deepagents-linux-arm64": "0.10.1-dev.6",
+    "@langchain/managed-deepagents-linux-x64": "0.10.1-dev.6",
+    "@langchain/managed-deepagents-win32-arm64": "0.10.1-dev.6",
+    "@langchain/managed-deepagents-win32-x64": "0.10.1-dev.6"
   },
   "peerDependencies": {
     "@browserbasehq/stagehand": "4.3.0",