Repository navigation
Utopia: run 0.1.0-re.8 (the importer reads utopia:temporal) - #2795
Conversation
|
Lore is reviewing this PR — 6dbba203-18b0-47b2-9eb8-a7f74860ca46. Submit a review that requests changes to have Lore push a fix for it. Comment |
🔍 Lore Spec ImpactExamined 1 changed file(s): 0 had graph data (no coupling found), 1 had none — no ingested test run covers them, so this check cannot speak for them. Deterministic · graph @ |
There was a problem hiding this comment.
Lore review — Approved
Clean Utopia image tag and sha256 digest bump to 0.1.0-re.8.
Must fix (0) · Consider (0) · Nits (0)
Reviewed by gemini-4-argon
Submit a review that requests changes to have Lore push a fix for it. Comment @lore review to re-run the review.
Posted by floor, visit c879bedf-a6dd-4836-bcea-72f28f3eeb02.
Bumps Utopia from
re.7to0.1.0-re.8(digestsha256:f8866e8c…). It puts deeplethe/utopia#1291 on the running Utopia: the ontology importer reads theutopia:temporalannotation its own export writes, so a relation in Lore's ontology can be an event or eternal instead of always a state. Utopia binds a pushed phrase by the declaration only when the relation is not a state (deeplethe/utopia#1242), so until this runs, none of Lore's mirrored phrases has been bound that way.re.8=re.7+ #1291 (issue deeplethe/utopia#1292), re-devf0587718, tagv0.1.0-re.8. Before tagging:cargo fmt --check,clippy -D warningsandcargo test --workspaceon the merged tree against a migrated test database, 1,615 passed and 0 failed. No new migration (still 0113).After merge:
terraform apply -target='kubernetes_deployment_v1.utopia[0]'from main. Then the ontology version stored for each mirrored repo is set back to 3, because #2790 deployed ontology v4 against re.7 and its upgrade imported every relation as a state; the next mirrored push re-imports v4 under re.8.Related: #2790 (ontology v4, the commit mirror), #2789 (re.7).
🤖 Generated with Claude Code