@stacklink/sdk 0.6.2 → 0.6.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.
package/README.md CHANGED
@@ -72,7 +72,7 @@ console.log(result.output ?? result.finalText);
72
72
 
73
73
  Reuse the returned `conversationId` for the next message. Preserve the last event sequence to resume observation. Published invocations are available through the existing session MCP endpoint using `STACKLINK_BOTS`; no separate server per bot is needed.
74
74
 
75
- ## Workflows (0.6.2)
75
+ ## Workflows (0.6.3)
76
76
 
77
77
  Use `https://api.stacklink.in` for production.
78
78
  Workflow trigger changes now follow draft → publish. `workflows.triggers(id)`
@@ -88,6 +88,11 @@ supported. Pausing blocks new starts; publishing does not resume a paused workfl
88
88
  The [Workflows guide](https://docs.stacklink.in/docs/workflows) covers definitions,
89
89
  permissions, stable job keys and recovery.
90
90
 
91
+ Drafting supports exact resource mentions. Use `workflows.searchMentions({ search, kind, offset, limit })` and `resolveMentions(references, workflowId)`
92
+ to discover and recheck permitted apps, Bots, workflows and saved API operations.
93
+ Pass optional `mentions` with UTF-16 `start`/`end` ranges to `suggest`; the server
94
+ rechecks access before drafting. A mention never grants permissions or connects an account.
95
+
91
96
  Embedded authoring uses the same workflow methods. Your backend calls
92
97
  `workflows.issueEmbeddedAccess` with the customer and person from its authenticated
93
98
  session. The separate `@stacklink/workflow-builder` browser package mounts the
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "schemaVersion": 1,
3
- "sdkVersion": "0.6.2",
3
+ "sdkVersion": "0.6.4",
4
4
  "node": ">=22.0.0",
5
5
  "tested": {
6
6
  "ai": "7.0.31",