@shinobiapps/shinobi 0.1.4 → 0.1.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 CHANGED
@@ -5,6 +5,46 @@ All notable changes to Shinobi will be documented in this file.
5
5
  The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
6
6
  and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
7
7
 
8
+ ## [0.1.6] — 2026-06-04
9
+
10
+ Dashboard UX: kanban/list naming + clickable subtask cards.
11
+
12
+ ### Changed
13
+
14
+ - **Renamed project tabs to match standard board/list nomenclature.**
15
+ "Kanban" → "Board", "Subtasks" → "List". The two tabs were already
16
+ showing the same project subtasks in different layouts (board grouped
17
+ by status vs. flat sortable table); the old labels falsely implied a
18
+ parent-child hierarchy ("Subtasks of what?"). URLs are unchanged so
19
+ bookmarks and external links keep working.
20
+
21
+ ### Added
22
+
23
+ - **Subtask detail drawer.** Clicking a card on the board or a row in
24
+ the list opens a slide-in drawer on the right with the full title,
25
+ description, status transitions, dependencies, files touched, and
26
+ timestamps. ESC and backdrop click close. Inline status buttons on
27
+ board cards still work (clicks inside them no longer open the drawer).
28
+
29
+ ## [0.1.5] — 2026-06-04
30
+
31
+ Bugfix release: the `prepare` lifecycle script no longer recurses on Windows.
32
+
33
+ ### Fixed
34
+
35
+ - **`prepare` script no longer loops on Windows when nested `npm`
36
+ invocations can't find `node` on `cmd.exe`'s PATH.** The previous
37
+ inline form was `node -e "...exists..." || (npm install --prefix
38
+ dashboard-spa && npm run build)`; on Windows, each nested `npm` call
39
+ spawned its own `cmd.exe`, and somewhere ~25 levels deep `node` fell
40
+ off PATH and the whole tree retried in a loop. Replaced with
41
+ `node scripts/prepare.mjs`, which does the dist-exists check directly
42
+ via `fs.existsSync` and short-circuits via `SHINOBI_PREPARE_RUNNING`
43
+ to break any future recursion. Only ever bit contributors cloning the
44
+ repo on Windows when node wasn't on the system `cmd.exe` PATH — npm
45
+ registry users were never affected (registry installs ship a prebuilt
46
+ `dist/` and don't run `prepare`).
47
+
8
48
  ## [0.1.4] — 2026-06-04
9
49
 
10
50
  Dashboard quality-of-life: project list now shows subtask completion at a glance.