Lambda 8550002878 fix(migrations): renumber issue properties to 179 and build the GIN index concurrently ...

main's migration sequence advanced twice under this PR (167 collision, then
an upstream renumber wave that claimed 178), so issue properties now sits at
179 — verified against main's current tip by the prefix-uniqueness lint.

The properties GIN index moves to its own single-statement migration (180)
using CREATE INDEX CONCURRENTLY — a plain CREATE INDEX on the hot issue
table would block writes for the duration of the build. Mirrors the
119_user_created_at_index pattern; full-chain dry-run on a fresh database
passes through 180.

Co-authored-by: multica-agent <github@multica.ai>

2026-07-14 17:30:11 +08:00

..

cmd

feat(server): custom issue properties — definitions, typed values, CLI (MUL-4463)

2026-07-14 17:29:00 +08:00

internal

fix(properties): address MUL-4463 review round 1 — mobile CI, option guard, mutation safety, schema tolerance

2026-07-14 17:29:00 +08:00

migrations

fix(migrations): renumber issue properties to 179 and build the GIN index concurrently

2026-07-14 17:30:11 +08:00

pkg

fix(properties): address MUL-4463 review round 1 — mobile CI, option guard, mutation safety, schema tolerance

2026-07-14 17:29:00 +08:00

go.mod

feat(daemon): bound daemon.log size with rotation (MUL-4330) (#5170)

2026-07-10 15:55:06 +08:00

go.sum

feat(daemon): bound daemon.log size with rotation (MUL-4330) (#5170)

2026-07-10 15:55:06 +08:00

sqlc.yaml

…