@jhizzard/termdeck-stack 0.2.4 → 0.2.6
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 +44 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -5,6 +5,50 @@ 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.6] — 2026-04-26
|
|
9
|
+
|
|
10
|
+
### Documentation
|
|
11
|
+
- Audit-trail update: validated against `@jhizzard/termdeck@0.6.7`,
|
|
12
|
+
which closes the loop on a long-standing flaw in the meta-installer
|
|
13
|
+
itself. The stack-installer writes
|
|
14
|
+
`SUPABASE_ACCESS_TOKEN: 'SUPABASE_PAT_HERE'` as a literal placeholder
|
|
15
|
+
string when wiring the Supabase MCP server entry into
|
|
16
|
+
`~/.claude/mcp.json` — the user is expected to manually replace it
|
|
17
|
+
after install. v0.6.4 told users to `export SUPABASE_ACCESS_TOKEN=...`
|
|
18
|
+
for `supabase link`, but that export never propagated into the JSON.
|
|
19
|
+
v0.6.7 of `@jhizzard/termdeck` now backfills the token automatically
|
|
20
|
+
during `termdeck init --rumen` once `supabase link` confirms the token
|
|
21
|
+
is real. See the root `CHANGELOG.md` v0.6.7 entry for the full helper
|
|
22
|
+
contract and the 10 regression fixtures.
|
|
23
|
+
|
|
24
|
+
### Notes
|
|
25
|
+
- This is the third audit-trail bump in the v0.6.5–v0.6.7 arc. No
|
|
26
|
+
installer behavior change — `npx @jhizzard/termdeck-stack` always
|
|
27
|
+
pulls `@jhizzard/termdeck@latest`. Future improvement: stop writing
|
|
28
|
+
the literal placeholder in this installer and instead skip the env
|
|
29
|
+
block when no real token is available, prompting the user to set
|
|
30
|
+
`SUPABASE_ACCESS_TOKEN` before running `init --rumen`. Tracked as a
|
|
31
|
+
follow-up; not blocking this audit-trail bump.
|
|
32
|
+
|
|
33
|
+
## [0.2.5] — 2026-04-26
|
|
34
|
+
|
|
35
|
+
### Documentation
|
|
36
|
+
- Audit-trail update: validated against `@jhizzard/termdeck@0.6.6`.
|
|
37
|
+
v0.6.6 auto-appends `?pgbouncer=true&connection_limit=1` on Supabase
|
|
38
|
+
transaction-pooler URLs (port 6543 on `*.pooler.supabase.com`),
|
|
39
|
+
closing the secondary warning Brad's Rumen logs showed alongside
|
|
40
|
+
the v0.6.5 schema error. Direct connections and session-mode pooler
|
|
41
|
+
URLs are unchanged. Detection lives in `setup/supabase-url.js`
|
|
42
|
+
(`isTransactionPoolerUrl`, `normalizeDatabaseUrl`) and is wired into
|
|
43
|
+
both `init-mnestra` (write time) and `init-rumen` (Edge Function
|
|
44
|
+
secret-set time, for partial-upgrade installs). 15 regression
|
|
45
|
+
fixtures pin the detection rules.
|
|
46
|
+
|
|
47
|
+
### Notes
|
|
48
|
+
- No installer behavior change. `npx @jhizzard/termdeck-stack` always
|
|
49
|
+
pulls `@jhizzard/termdeck@latest`. Mnestra and Rumen versions are
|
|
50
|
+
unchanged through this bump (0.2.2 and 0.4.3 respectively).
|
|
51
|
+
|
|
8
52
|
## [0.2.4] — 2026-04-26
|
|
9
53
|
|
|
10
54
|
### Documentation
|
package/package.json
CHANGED