@jhizzard/termdeck-stack 0.2.1 → 0.2.3
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 +43 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -5,6 +5,49 @@ underlying packages (`@jhizzard/termdeck`, `@jhizzard/mnestra`,
|
|
|
5
5
|
`@jhizzard/rumen`) ship on their own cadences and have their own
|
|
6
6
|
changelogs — see the root `CHANGELOG.md` for `@jhizzard/termdeck`.
|
|
7
7
|
|
|
8
|
+
## [0.2.3] — 2026-04-26
|
|
9
|
+
|
|
10
|
+
### Documentation
|
|
11
|
+
- Audit-trail update: validated against `@jhizzard/termdeck@0.6.4`,
|
|
12
|
+
which surfaced after v0.6.3 unblocked `init --mnestra` for Brad's
|
|
13
|
+
MobaXterm SSH install — the next step (`init --rumen`) failed with
|
|
14
|
+
the Supabase CLI's raw *"Access token not provided"* error. v0.6.4
|
|
15
|
+
detects that signature and prints a path-aware hint pointing at
|
|
16
|
+
the Supabase PAT dashboard plus the exact `export` command, since
|
|
17
|
+
`supabase login` (the CLI's other suggestion) requires a browser
|
|
18
|
+
and doesn't work over SSH. v0.6.4 also adds `termdeck init --mnestra
|
|
19
|
+
--from-env` as a defensive non-interactive bypass for any terminal
|
|
20
|
+
that fights with our raw-mode secret prompt. See the root
|
|
21
|
+
`CHANGELOG.md` for the full v0.6.4 entry.
|
|
22
|
+
|
|
23
|
+
### Notes
|
|
24
|
+
- No installer behavior change. `npx @jhizzard/termdeck-stack` always
|
|
25
|
+
pulls `@jhizzard/termdeck@latest`, so existing 0.2.x installs pick
|
|
26
|
+
up v0.6.4 automatically. Brad confirmed the cache trap on 0.6.0
|
|
27
|
+
the hard way; users who hit similar staleness should always run
|
|
28
|
+
`npm cache clean --force && npm i -g @jhizzard/termdeck@latest`
|
|
29
|
+
(or just re-run `npx @jhizzard/termdeck-stack`).
|
|
30
|
+
|
|
31
|
+
## [0.2.2] — 2026-04-25
|
|
32
|
+
|
|
33
|
+
### Documentation
|
|
34
|
+
- Audit-trail update: validated against `@jhizzard/termdeck@0.6.3`,
|
|
35
|
+
which shipped after a fourth report from the same tester whose
|
|
36
|
+
pre-v0.6.1 install was already half-set-up. v0.6.3 reorders
|
|
37
|
+
`termdeck init --mnestra` to persist `~/.termdeck/secrets.env`
|
|
38
|
+
immediately after collecting inputs (before any pg work), so a
|
|
39
|
+
failed Postgres connect no longer throws away the typed-in
|
|
40
|
+
`DATABASE_URL`. It also adds `--yes` (reuse saved secrets, skip
|
|
41
|
+
prompts) and `--reset` (ignore saved secrets, re-prompt). See the
|
|
42
|
+
root `CHANGELOG.md` for the full v0.6.3 entry.
|
|
43
|
+
|
|
44
|
+
### Notes
|
|
45
|
+
- No installer behavior change. `npx @jhizzard/termdeck-stack` always
|
|
46
|
+
pulls `@jhizzard/termdeck@latest`, so existing 0.2.x installs pick
|
|
47
|
+
up the v0.6.3 wizard fix automatically. This bump keeps the audit
|
|
48
|
+
trail tight — the CHANGELOG for 0.2.1 was written before the
|
|
49
|
+
fourth tester report came in.
|
|
50
|
+
|
|
8
51
|
## [0.2.1] — 2026-04-25
|
|
9
52
|
|
|
10
53
|
### Documentation
|
package/package.json
CHANGED