kanbo-cli 0.3.0 → 0.5.0

package/dist/drizzle-postgres/0006_flow_rules_and_column_entries.sql

@@ -0,0 +1,3 @@
+ALTER TABLE "issue_statuses" ADD COLUMN "allowed_from" text;--> statement-breakpoint
+ALTER TABLE "issue_statuses" ADD COLUMN "wip_limit" integer;--> statement-breakpoint
+CREATE INDEX "issue_field_changes_field_created_at_idx" ON "issue_field_changes" USING btree ("field","created_at");

package/dist/drizzle-postgres/README.md

@@ -51,6 +51,14 @@ applied by `kanbo migrate` (`migrateBoardDatabase`) and by nothing else.
   `ADD COLUMN`, no new sequence, so no new grant. The epoch stays 1; a
   database still at 0004 reads as `board_schema_outdated` (`missingColumns`)
   until `kanbo migrate` has run.
+- **0006_flow_rules_and_column_entries.sql**: `issue_statuses.allowed_from`
+  (text, a JSON array of the status ids a card may enter the column from,
+  nullable — `null` for any column, `[]` for none) and `issue_statuses.wip_limit`
+  (integer, the most cards the column holds, nullable): the column's flow rules
+  (board-workflow spec, Part 2). And `issue_field_changes_field_created_at_idx`
+  on `(field, created_at)`, which the column-entry feed reads by. Two plain
+  `ADD COLUMN`s and a `CREATE INDEX`. No new sequence, so no new grant. The epoch stays 1; a database still at 0005
+  reads as `board_schema_outdated` (`missingColumns`) until `kanbo migrate` has run.
 - **meta/**: the drizzle journal and schema snapshots. JSON only, or
   `drizzle-kit generate` fails to parse the directory.