prjct-cli 2.1.1 → 2.1.2
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/dist/bin/prjct-core.mjs +202 -202
- package/dist/daemon/entry.mjs +148 -148
- package/dist/mcp/server.mjs +1 -1
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,48 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## [2.1.2] - 2026-04-22
|
|
4
|
+
|
|
5
|
+
Upgrade-safety pass for clients coming from 1.x or 2.1.0. The 2.1.1
|
|
6
|
+
release fixed the CLI surface but left two upgrade hazards that clients
|
|
7
|
+
could hit in the wild.
|
|
8
|
+
|
|
9
|
+
### Fixed
|
|
10
|
+
- **Zombie daemon after global upgrade.** pnpm's content-addressable
|
|
11
|
+
store leaves the previous-version files untouched on disk when a new
|
|
12
|
+
version is installed globally, so the long-lived daemon kept serving
|
|
13
|
+
requests from the old build. The thin shim's mtime-based stale check
|
|
14
|
+
never fired. Daemon now reads its own `package.json` at startup,
|
|
15
|
+
periodically probes the globally-installed `prjct` binary
|
|
16
|
+
(pnpm/npm/volta/asdf paths covered), and shuts itself down on
|
|
17
|
+
version mismatch — the next request spawns a fresh daemon.
|
|
18
|
+
(`core/daemon/daemon.ts`)
|
|
19
|
+
- **Orphan `workflow_rules` after v1 → v2.** v1 users could attach hooks
|
|
20
|
+
to command verbs that v2 narrowed `HookCommand` to `[task, done,
|
|
21
|
+
ship, sync]`. Rules keyed on `pause/resume/reopen/next/dash/bug/idea/
|
|
22
|
+
linear/jira/tokens/velocity/plan` survived the upgrade as dead rows
|
|
23
|
+
that `prjct workflow list` still surfaced. SQLite migration v15
|
|
24
|
+
disables them idempotently (enabled=0, not deleted — visible with
|
|
25
|
+
`--include-disabled` for rename/re-enable). Only the orphans —
|
|
26
|
+
`done/ship/task/sync` hooks are preserved.
|
|
27
|
+
(`core/storage/database.ts`, migration v15)
|
|
28
|
+
|
|
29
|
+
### Added
|
|
30
|
+
- Upgrade-path test coverage in
|
|
31
|
+
`core/__tests__/storage/upgrade-v1-to-v2.test.ts`: seeds a v1-shaped
|
|
32
|
+
DB, asserts orphan rules are disabled, valid hooks survive, and the
|
|
33
|
+
legacy task-status values (`in_progress`/`done`/etc.) still coerce
|
|
34
|
+
correctly through the state machine.
|
|
35
|
+
|
|
36
|
+
### Migration notes
|
|
37
|
+
|
|
38
|
+
- Upgrading from 1.x: no action required. On first `prjct <cmd>` after
|
|
39
|
+
install, any stale daemon detects the version drift and exits; the
|
|
40
|
+
next invocation starts a clean daemon and runs migration v15 the
|
|
41
|
+
first time each project's DB is touched.
|
|
42
|
+
- Orphan rules show as `disabled` in `prjct workflow list
|
|
43
|
+
--include-disabled`. Rename their `command` to a v2 `HookCommand`
|
|
44
|
+
value (`task`/`done`/`ship`/`sync`) and re-enable if still relevant.
|
|
45
|
+
|
|
3
46
|
## [2.1.1] - 2026-04-22
|
|
4
47
|
|
|
5
48
|
Closes the v2 migration gap shipped (incompletely) in `2.1.0` and
|