@pikku/skills 0.12.55 → 0.12.57
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/package.json
CHANGED
|
@@ -61,6 +61,25 @@ group's lease, done — and when a held or leased item is **claimable at** (a lo
|
|
|
61
61
|
cannot be taken. For held items, run `wait --claim` rather than retrying. The lease is 30 minutes
|
|
62
62
|
(`--lease-minutes`); an abandoned claim returns to the queue by itself.
|
|
63
63
|
|
|
64
|
+
## The board
|
|
65
|
+
|
|
66
|
+
Every change sits in one column: backlog, ready, in progress, needs answer, done.
|
|
67
|
+
`list` prints them left to right with counts (`--include-done` adds done). A claim is
|
|
68
|
+
not a column: it lives on the changeset's lease, so a change still in progress whose
|
|
69
|
+
lease lapsed shows as `abandoned`, and `next` and `wait` pick it up again.
|
|
70
|
+
|
|
71
|
+
`claim`, `wait` and `next` never take a backlog change; `claim` on one is refused
|
|
72
|
+
with a 409. Move it first, and only when the person asked for it to be worked:
|
|
73
|
+
|
|
74
|
+
```bash
|
|
75
|
+
pikku changes ready 5 # backlog → ready
|
|
76
|
+
pikku changes backlog 5 # shelve it again
|
|
77
|
+
pikku changes start 3 4 # ready → in progress, the work has begun
|
|
78
|
+
```
|
|
79
|
+
|
|
80
|
+
The backlog lives in the local queue only; a project whose changes are in Pikku
|
|
81
|
+
Studio Cloud refuses `backlog`, `ready` and `file --backlog`.
|
|
82
|
+
|
|
64
83
|
## Changesets
|
|
65
84
|
|
|
66
85
|
Group related items into changesets and claim each one as a group, saying which tables it touches —
|
|
@@ -64,7 +64,9 @@ to learn a dependency is vulnerable; use `update` to move Pikku itself.
|
|
|
64
64
|
- Coverage is the nearest package.json walking up from the project root, plus
|
|
65
65
|
every workspace it declares — a monorepo updates in one pass. All four
|
|
66
66
|
dependency fields are read, `peerDependencies` included, so an addon's own
|
|
67
|
-
declared peer range moves with it.
|
|
67
|
+
declared peer range moves with it. `overrides` and `resolutions` move too —
|
|
68
|
+
an override left behind pins the old version over the new range. A nested
|
|
69
|
+
override (an object, not a version) is left alone.
|
|
68
70
|
|
|
69
71
|
Statuses, per dependency: `outdated` (the range floor is behind latest — this is
|
|
70
72
|
what `--update` writes), `stale-install` (the range already admits latest but
|