@stackbone/cli 0.6.0 → 0.6.1
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 +27 -0
- package/main.js +2229 -1857
- package/package.json +1 -1
- package/stackbone-cli-0.6.1.tgz +0 -0
- package/stackbone-cli-0.6.0.tgz +0 -0
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.6.1] - 2026-10-08
|
|
11
|
+
|
|
12
|
+
### Added
|
|
13
|
+
|
|
14
|
+
- **`stackbone dev` says so when the organization's trial has ended.** The
|
|
15
|
+
control plane refuses the tunnel grant and the local registration of an
|
|
16
|
+
organization whose trial is over with `trial_expired`. The CLI prints that
|
|
17
|
+
the trial ended, that nothing was deleted and how to continue, exits `5`, and
|
|
18
|
+
does not retry. `stackbone init` reads the same refusal the same way. A
|
|
19
|
+
session that was already running keeps running (PLA-2036).
|
|
20
|
+
- **`stackbone link` stops at an ended trial too.** The control plane now also
|
|
21
|
+
refuses `trial_expired` when an organization whose trial is over registers a
|
|
22
|
+
box (`link`) or creates a workspace (`init`), so both commands print the same
|
|
23
|
+
trial-ended message and exit `5` (PLA-2037).
|
|
24
|
+
|
|
25
|
+
### Security
|
|
26
|
+
|
|
27
|
+
- **A `stackbone dev` box no longer verifies connector calls with a key from
|
|
28
|
+
the public repo.** Every dev box signed `/api/connect/*` with the same
|
|
29
|
+
constant and encrypted connected accounts under the same key, so anyone
|
|
30
|
+
holding a tunnel URL could mint tokens for the creator's Gmail, Slack or
|
|
31
|
+
HubSpot. Each dev box now mints its own pair on its first boot and keeps it
|
|
32
|
+
in its own dev Postgres, next to the connections it protects. Connections
|
|
33
|
+
made with an older CLI are moved onto the new key at boot and keep working;
|
|
34
|
+
one that no known key can open is removed with a warning, and you reconnect
|
|
35
|
+
it in Studio (PLA-1866).
|
|
36
|
+
|
|
10
37
|
## [0.6.0] - 2026-10-06
|
|
11
38
|
|
|
12
39
|
### Added
|