mirror of
https://github.com/hanzoai/insights.git
synced 2026-10-30 16:15:31 +00:00
zeekay
1b367e2b62
The tree was a debranded snapshot of upstream taken around 2026-02-20, and upstream has moved about five months since. This replaces it with upstream master, mechanically re-derived: bin/debrand does the rename, and the pipeline and squashed migrations are restored from the shipped tree. Not a merge. The previous import replaced the tree wholesale in a single commit, so there is no shared content history to merge against. Reproducing the rename on the new tree is what actually converges. What survives: .hanzo/workflows, the Dockerfiles and bin/docker* entrypoints, compose files, LLM.md, and insights/migrations. The squashed initial migration is load-bearing — the live database records it by name, so upstream's ~918 individual migrations cannot come back. Nine products are dropped as unreferenced. Twenty-one more that we do not run are kept anyway because the core app still imports them; unpicking those is a refactor and does not belong in a rebase. This base does not build yet, and the reasons are not in the rename: upstream now wants Python 3.13.13 against our 3.12.12 and Django 5.2 against our 4.2, and the dependency manifests still name upstream packages that we republish under our own names. Those are decisions, not renames.
11 lines
602 B
SQL
11 lines
602 B
SQL
-- The wait-until-event feature is not yet live, so we drop existing data and
|
|
-- re-create the column as TEXT so non-UUID person identifiers (UUIDT, group keys)
|
|
-- flow through without coercion.
|
|
--
|
|
-- DROP + ADD in a single ALTER keeps the column atomic from other sessions'
|
|
-- view: they see the table either with the old UUID column or with the new TEXT
|
|
-- column, never with no `person_id` at all. The dependent index is dropped here
|
|
-- and recreated CONCURRENTLY in the next migration.
|
|
SET lock_timeout = '5s';
|
|
ALTER TABLE cyclotron_jobs DROP COLUMN IF EXISTS person_id, ADD COLUMN person_id TEXT;
|