Skip to content

Pin Nucleus v1.2.1 (upstream fix for the L9 ALTER corruption) - #3

Merged
im-tyler merged 1 commit into
mainfrom
chore/nucleus-v1.2.1
Oct 4, 2026
Merged

im-tyler merged 1 commit into
mainfrom
chore/nucleus-v1.2.1

Conversation

@im-tyler

@im-tyler im-tyler commented Oct 4, 2026

Copy link
Copy Markdown
Contributor

Nucleus v1.2.1 shipped today with the upstream fix behind L9: ALTER TABLE ADD/DROP COLUMN and ALTER COLUMN TYPE are now all-or-nothing on the disk stack (layout adopted, every row rewritten, indexes rebuilt, every tuple verified to decode; any failure restores the pre-change state), and half-applied ALTERs are no longer recorded as migrated — the state that left live llm_traces undecodable with token_source present and cost_source missing after migration 054.

Changes:

  • teploy.yml: pin ghcr.io/neutron-build/nucleus:v1.2.1 with the dated changelog comment (convention), including the pointer to the in-place catalog repair the infra-home store still needs before 054 can re-run.
  • ci.yml: new NUCLEUS_VERSION workflow env (single bump point); both integration jobs now reference it; step names de-versioned. Same shape the S1 branch introduced, so that merge converges to one line.
  • docker-compose.yml: pinned (was :latest) via ${NUCLEUS_VERSION:-v1.2.1}.
  • AUDIT_OPEN.md: L9 updated — upstream resolved; (b) no longer needed for correctness on v1.2.1+ (the engine refuses ALTER-after-write orderings itself); (c) covered by the S1 populated-upgrade test; (a) remains an owner op, now with the row-preserving in-place repair instead of rename-aside loss.

Verified before bumping, exact CI shape (fresh v1.2.1 container, migration boot 001-056, then go test -p 1 ./... with OBSERVE_REQUIRE_NUCLEUS=1): 48 packages, all green.

Migration files intentionally unchanged — ADD COLUMN IF NOT EXISTS is safe again on this engine per the upstream handover (nucleus/docs/HANDOVER_TEPLOY_OBSERVE_ADD_COLUMN.md).

teploy.yml, CI (new NUCLEUS_VERSION env, both integration jobs) and
docker-compose (was :latest) now pin ghcr.io/neutron-build/nucleus:v1.2.1,
which makes ADD/DROP COLUMN and ALTER TYPE atomic on the disk stack and
stops half-applied ALTERs being recorded as migrated — the engine defects
behind L9 (live llm_traces undecodable after migration 054). Verified
before bumping, CI shape (fresh engine, migration boot 001-056, -p 1):
48 packages green. AUDIT_OPEN L9 updated: upstream resolved, repair
re-scoped to the in-place catalog fix from the Neutron handover doc.
Migration files unchanged — ALTER-ADD is safe again on this engine, and
it now refuses ALTER-after-write orderings itself.
@im-tyler
im-tyler merged commit eaf17c0 into main Oct 4, 2026
11 checks passed
@im-tyler
im-tyler deleted the chore/nucleus-v1.2.1 branch October 4, 2026 06:20
@im-tyler
im-tyler restored the chore/nucleus-v1.2.1 branch October 4, 2026 06:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant