@stackbone/sdk 0.1.0-alpha.7 → 0.1.0-alpha.8

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/CHANGELOG.md CHANGED
@@ -7,6 +7,27 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
7
7
 
8
8
  ## [Unreleased]
9
9
 
10
+ ## [0.1.0-alpha.8] - 2026-07-01
11
+
12
+ ### Added
13
+
14
+ - **`stackbone.workflows` — namespaced workflow trigger + schedule surface on the
15
+ ambient client.** `stackbone.workflows.start(name, input)` (fire-and-forget),
16
+ `.startAndWait<T>(name, input)` (durable sub-routine), `.schedule(name, input,
17
+ cron)` / `.unschedule(name)` / `.listSchedules()` (dynamic cron). These are the
18
+ peer-free shims over the runtime-injected `WorkflowStarter` / `WorkflowScheduler`
19
+ seams, now exposed under one unified `stackbone.*` namespace alongside
20
+ `stackbone.connection` / `stackbone.agent`. The main barrel stays peer-free.
21
+
22
+ ### Deprecated
23
+
24
+ - The loose `startWorkflow` / `startWorkflowAndWait` / `scheduleWorkflow` /
25
+ `unschedule` / `listSchedules` exports on the `@stackbone/sdk/workflow` subpath
26
+ are now `@deprecated` aliases that delegate to the identical implementation —
27
+ prefer the namespaced `stackbone.workflows.*` members. The peer-bound authoring
28
+ API (`requestApproval` / `defineHook` / `sleep`) stays on the subpath because it
29
+ eager-loads the `workflow` peer.
30
+
10
31
  ## [0.1.0-alpha.7] - 2026-06-25
11
32
 
12
33
  ### Added