@stackbone/sdk 0.1.0-alpha.7 → 0.1.0

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,33 @@ 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] - 2026-07-01
11
+
12
+ ### Changed
13
+
14
+ - **First stable release.** No API changes since `0.1.0-alpha.8`; promotes the SDK to a stable line so `npm i @stackbone/sdk` resolves it through the `latest` dist-tag and generated projects can pin it exactly.
15
+
16
+ ## [0.1.0-alpha.8] - 2026-07-01
17
+
18
+ ### Added
19
+
20
+ - **`stackbone.workflows` — namespaced workflow trigger + schedule surface on the
21
+ ambient client.** `stackbone.workflows.start(name, input)` (fire-and-forget),
22
+ `.startAndWait<T>(name, input)` (durable sub-routine), `.schedule(name, input,
23
+ cron)` / `.unschedule(name)` / `.listSchedules()` (dynamic cron). These are the
24
+ peer-free shims over the runtime-injected `WorkflowStarter` / `WorkflowScheduler`
25
+ seams, now exposed under one unified `stackbone.*` namespace alongside
26
+ `stackbone.connection` / `stackbone.agent`. The main barrel stays peer-free.
27
+
28
+ ### Deprecated
29
+
30
+ - The loose `startWorkflow` / `startWorkflowAndWait` / `scheduleWorkflow` /
31
+ `unschedule` / `listSchedules` exports on the `@stackbone/sdk/workflow` subpath
32
+ are now `@deprecated` aliases that delegate to the identical implementation —
33
+ prefer the namespaced `stackbone.workflows.*` members. The peer-bound authoring
34
+ API (`requestApproval` / `defineHook` / `sleep`) stays on the subpath because it
35
+ eager-loads the `workflow` peer.
36
+
10
37
  ## [0.1.0-alpha.7] - 2026-06-25
11
38
 
12
39
  ### Added