@shinobiapps/shinobi 0.1.3 → 0.1.5

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,51 @@ 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.5] — 2026-06-04
9
+
10
+ Bugfix release: the `prepare` lifecycle script no longer recurses on Windows.
11
+
12
+ ### Fixed
13
+
14
+ - **`prepare` script no longer loops on Windows when nested `npm`
15
+ invocations can't find `node` on `cmd.exe`'s PATH.** The previous
16
+ inline form was `node -e "...exists..." || (npm install --prefix
17
+ dashboard-spa && npm run build)`; on Windows, each nested `npm` call
18
+ spawned its own `cmd.exe`, and somewhere ~25 levels deep `node` fell
19
+ off PATH and the whole tree retried in a loop. Replaced with
20
+ `node scripts/prepare.mjs`, which does the dist-exists check directly
21
+ via `fs.existsSync` and short-circuits via `SHINOBI_PREPARE_RUNNING`
22
+ to break any future recursion. Only ever bit contributors cloning the
23
+ repo on Windows when node wasn't on the system `cmd.exe` PATH — npm
24
+ registry users were never affected (registry installs ship a prebuilt
25
+ `dist/` and don't run `prepare`).
26
+
27
+ ## [0.1.4] — 2026-06-04
28
+
29
+ Dashboard quality-of-life: project list now shows subtask completion at a glance.
30
+
31
+ ### Added
32
+
33
+ - **Project progress bar in the dashboard table.** New "Progress" column
34
+ renders a slim bar plus `done/total · %` text next to every project.
35
+ Color tier: emerald when 100% done, accent when ≥ 50%, amber under 50%,
36
+ em dash when the project has no subtasks. `role="progressbar"` with
37
+ `aria-valuenow` for screen readers.
38
+ - **Backend exposes `subtasks_total` + `subtasks_done` on every project
39
+ read path.** `listProjects`, `getProject`, and `projectsMatchingTargetPath`
40
+ now LEFT JOIN a subtask aggregate subquery and surface both counts on
41
+ the `Project` type. The `/api/projects` endpoint returns them without
42
+ any extra round-trips.
43
+
44
+ ### Why
45
+
46
+ The project list used to show only `project.status` (`todo` / `in_progress`
47
+ / `done`), which is operator-set and frequently lags behind the real subtask
48
+ state — projects sat at "todo" while every subtask was already done. Users
49
+ had to drill into each project just to see whether work was actually
50
+ finished. The progress column closes that loop without changing the
51
+ operator-controlled status semantics.
52
+
8
53
  ## [0.1.3] — 2026-05-29
9
54
 
10
55
  Pre-launch polish: multi-client MCP bootstrap.
@@ -46,7 +46,7 @@ Instances of unacceptable behavior may be reported to the project
46
46
  maintainer at:
47
47
 
48
48
  ```
49
- contact@shinobi-apps.hr
49
+ contact@shinobi-apps.com
50
50
  ```
51
51
 
52
52
  All complaints will be reviewed and investigated promptly and fairly. The