@stackbone/cli 0.6.0 → 0.6.2

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,73 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
7
7
 
8
8
  ## [Unreleased]
9
9
 
10
+ ## [0.6.2] - 2026-10-09
11
+
12
+ ### Added
13
+
14
+ - **`stackbone triggers list` — the trigger links, and which may start
15
+ themselves.** Lists every trigger → workflow link of an installation: its id,
16
+ on or off, the connector and trigger it reads, and the workflow it starts. A
17
+ link whose runs wrote back through its own connector with an `echoPath` and
18
+ never asked `isOwnEcho` about it in the last hour gets a `warning:` line
19
+ under it, naming the connector and the operation, in the same words as the
20
+ banner on the trigger's page in Studio. The JSON carries it as
21
+ `activity.echoLoop` (PLA-1580).
22
+
23
+ - **`stackbone runs` names the trigger link that started a run.** `runs get`
24
+ prints a `link` line, `Gmail · New Email (started)`, and `runs list` ends the
25
+ row of a linked run with the same names. The JSON carries the link as
26
+ `triggerLink`, with the names the box's connector catalog gives it. A
27
+ connector the catalog does not list prints its ids (PLA-1898).
28
+
29
+ ### Changed
30
+
31
+ - **Every connector comes from the Activepieces catalog.** `stackbone dev`
32
+ reads the catalog published for the runtime's pin at `catalog.stackbone.ai`,
33
+ checks it against its digest, and lists the pieces the execution sweep
34
+ proved, 718 today. A piece's code downloads the first time one of its
35
+ actions runs. When the catalog cannot be reached at boot, the box starts
36
+ with no pieces and logs the URL it tried (PLA-1662, PLA-1908).
37
+ - **The hand-written built-ins retire, and their pieces take the ids.**
38
+ `google-drive`, `gmail`, `github`, `linear`, `stripe` and `supabase` are now
39
+ pieces under the same id, with the piece's operation names:
40
+ `drive_list_files`, not `drive.files.list`; `send_email` on Gmail;
41
+ `rawGraphqlQuery` on Linear. A connection registered with an older CLI must
42
+ be registered again, and a trigger link on a built-in trigger recreated on
43
+ the piece's trigger. An `outlook-app-only` connection converts to
44
+ `microsoft-outlook` on boot, links included (PLA-1911, PLA-1978, PLA-1932,
45
+ PLA-1982, PLA-1983, PLA-1984, PLA-1985).
46
+ - **A piece's triggers run in the box.** Polling triggers poll from the box,
47
+ and webhook triggers register at the provider and start a run on each
48
+ delivery (PLA-1855, PLA-1856).
49
+
50
+ ## [0.6.1] - 2026-10-08
51
+
52
+ ### Added
53
+
54
+ - **`stackbone dev` says so when the organization's trial has ended.** The
55
+ control plane refuses the tunnel grant and the local registration of an
56
+ organization whose trial is over with `trial_expired`. The CLI prints that
57
+ the trial ended, that nothing was deleted and how to continue, exits `5`, and
58
+ does not retry. `stackbone init` reads the same refusal the same way. A
59
+ session that was already running keeps running (PLA-2036).
60
+ - **`stackbone link` stops at an ended trial too.** The control plane now also
61
+ refuses `trial_expired` when an organization whose trial is over registers a
62
+ box (`link`) or creates a workspace (`init`), so both commands print the same
63
+ trial-ended message and exit `5` (PLA-2037).
64
+
65
+ ### Security
66
+
67
+ - **A `stackbone dev` box no longer verifies connector calls with a key from
68
+ the public repo.** Every dev box signed `/api/connect/*` with the same
69
+ constant and encrypted connected accounts under the same key, so anyone
70
+ holding a tunnel URL could mint tokens for the creator's Gmail, Slack or
71
+ HubSpot. Each dev box now mints its own pair on its first boot and keeps it
72
+ in its own dev Postgres, next to the connections it protects. Connections
73
+ made with an older CLI are moved onto the new key at boot and keep working;
74
+ one that no known key can open is removed with a warning, and you reconnect
75
+ it in Studio (PLA-1866).
76
+
10
77
  ## [0.6.0] - 2026-10-06
11
78
 
12
79
  ### Added