@jhizzard/termdeck-stack 0.2.2 → 0.2.4
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 +48 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -5,6 +5,54 @@ 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.4] — 2026-04-26
|
|
9
|
+
|
|
10
|
+
### Documentation
|
|
11
|
+
- Audit-trail update: validated against `@jhizzard/termdeck@0.6.5` and
|
|
12
|
+
`@jhizzard/mnestra@0.2.2`, both shipped 2026-04-26 to fix a schema
|
|
13
|
+
drift between the published Mnestra migrations and Rumen's runtime
|
|
14
|
+
contract. The `memory_items.source_session_id` column existed in the
|
|
15
|
+
pre-rebrand `rag-system` schema but was dropped from the published
|
|
16
|
+
Mnestra migrations during the Engram → Mnestra rename. Rumen v0.4.x
|
|
17
|
+
still required it, so every fresh `termdeck init --mnestra` →
|
|
18
|
+
`termdeck init --rumen` install path failed Rumen's first cron tick
|
|
19
|
+
with `column m.source_session_id does not exist`. Both packages now
|
|
20
|
+
ship migration `007_add_source_session_id.sql` (idempotent, TEXT,
|
|
21
|
+
partial index). See the root `CHANGELOG.md` v0.6.5 entry and
|
|
22
|
+
`@jhizzard/mnestra` v0.2.2 entry for full context.
|
|
23
|
+
|
|
24
|
+
### Notes
|
|
25
|
+
- This is the first release where two underlying packages bumped
|
|
26
|
+
together as a coordinated set. The meta-installer behavior is
|
|
27
|
+
unchanged — `npx @jhizzard/termdeck-stack` always pulls each layer's
|
|
28
|
+
`@latest`, so a fresh run picks up both fixes automatically. Anyone
|
|
29
|
+
on a partially-installed v0.6.4 stack should run
|
|
30
|
+
`termdeck init --mnestra --yes` after upgrading; the new migration
|
|
31
|
+
applies idempotently without re-prompting for credentials.
|
|
32
|
+
|
|
33
|
+
## [0.2.3] — 2026-04-26
|
|
34
|
+
|
|
35
|
+
### Documentation
|
|
36
|
+
- Audit-trail update: validated against `@jhizzard/termdeck@0.6.4`,
|
|
37
|
+
which surfaced after v0.6.3 unblocked `init --mnestra` for Brad's
|
|
38
|
+
MobaXterm SSH install — the next step (`init --rumen`) failed with
|
|
39
|
+
the Supabase CLI's raw *"Access token not provided"* error. v0.6.4
|
|
40
|
+
detects that signature and prints a path-aware hint pointing at
|
|
41
|
+
the Supabase PAT dashboard plus the exact `export` command, since
|
|
42
|
+
`supabase login` (the CLI's other suggestion) requires a browser
|
|
43
|
+
and doesn't work over SSH. v0.6.4 also adds `termdeck init --mnestra
|
|
44
|
+
--from-env` as a defensive non-interactive bypass for any terminal
|
|
45
|
+
that fights with our raw-mode secret prompt. See the root
|
|
46
|
+
`CHANGELOG.md` for the full v0.6.4 entry.
|
|
47
|
+
|
|
48
|
+
### Notes
|
|
49
|
+
- No installer behavior change. `npx @jhizzard/termdeck-stack` always
|
|
50
|
+
pulls `@jhizzard/termdeck@latest`, so existing 0.2.x installs pick
|
|
51
|
+
up v0.6.4 automatically. Brad confirmed the cache trap on 0.6.0
|
|
52
|
+
the hard way; users who hit similar staleness should always run
|
|
53
|
+
`npm cache clean --force && npm i -g @jhizzard/termdeck@latest`
|
|
54
|
+
(or just re-run `npx @jhizzard/termdeck-stack`).
|
|
55
|
+
|
|
8
56
|
## [0.2.2] — 2026-04-25
|
|
9
57
|
|
|
10
58
|
### Documentation
|
package/package.json
CHANGED