update migration docs (#461)

* update migration docs * Update docs/build/project-upgrades.md * Update docs/build/project-upgrades.md --------- Co-authored-by: James Bayly <[email protected]>
subquery · Dec 22, 2023 · 4b1bce8 · 4b1bce8
1 parent 1b07eeb
commit 4b1bce8
Showing 1 changed file with 1 addition and 2 deletions.
diff --git a/docs/build/project-upgrades.md b/docs/build/project-upgrades.md
@@ -59,7 +59,6 @@ These are in addition to [Project Upgrade requirements](#requirements):
 ### Supported Migrations
 
 Supported migrations:
-
 - Adding new entities
 - Removing entities (this is destructive)
 - Adding new fields (however only [nullable fields](./graphql.md#entities) are supported)
@@ -70,9 +69,9 @@ Supported migrations:
   - Please note: When field update is detected, the original field column will be dropped (with all existing data in that field), and a new column will be created with the new field types.
 
 Other notes:
-
 - Only supports PostgreSQL stores
 - Does not support adding new [foreign key relations](./graphql.md#entity-relationships)
 - Does not support enum creation or removal
 - Migrations will not succeed `--unfinalizedBlocks` is enabled
 - [GraphQL subscriptions](../run_publish/subscription.md) are not supported
+- [Rewind](../run_publish/historical.md) will only be supported if the new schema does not drop any `fields` or `entity`. Note that [automated historical state tracking](../run_publish/historical.md) must be enabled to support rewind.