omnigraph/crates
aaltshuler 466af5bc95 test(compiler): pin the rename+widen interaction — rename first, ExtendEnum names the new property
Greptile review follow-up: a property renamed and widened in one
migration emits RenameProperty followed by ExtendEnum carrying the
post-rename name. That ordering/naming contract is now stated on the
ExtendEnum variant's doc and pinned by
plan_orders_rename_before_widening_and_names_the_new_property, so a
sequential step consumer (or a future apply-ordering change) can't
silently break it.
2026-07-05 01:32:11 +03:00
..
omnigraph feat(engine): apply ExtendEnum as a metadata-only schema step 2026-07-05 01:32:11 +03:00
omnigraph-api-types chore(release): bump version to 0.8.0 (#313) 2026-06-29 12:38:24 +02:00
omnigraph-cli feat(compiler): plan pure enum widening as a supported ExtendEnum step 2026-07-05 01:32:11 +03:00
omnigraph-cluster chore(release): bump version to 0.8.0 (#313) 2026-06-29 12:38:24 +02:00
omnigraph-compiler test(compiler): pin the rename+widen interaction — rename first, ExtendEnum names the new property 2026-07-05 01:32:11 +03:00
omnigraph-policy chore(release): bump version to 0.8.0 (#313) 2026-06-29 12:38:24 +02:00
omnigraph-server chore(release): bump version to 0.8.0 (#313) 2026-06-29 12:38:24 +02:00