Removing `:context` multitenancy generates invalid migrations

[serpent213]

Versions

Elixir 1.18.3, latest stable deps
PgSQL 17

Operating system

macOS/Nix

Current Behavior

mix ash.reset
mix ash_postgres.generate_migrations --dev
mix ash.migrate

↓

10:09:16.855 [info] == Running 20250706080910 Demo.Repo.Migrations.MigrateResources1.up/0 forward

10:09:16.856 [info] create table users

10:09:16.858 [info] drop constraint api_keys_user_id_fkey from table api_keys
** (Postgrex.Error) ERROR 42704 (undefined_object) constraint "api_keys_user_id_fkey" of relation "api_keys" does not exist
    (ecto_sql 3.13.2) lib/ecto/adapters/sql.ex:1098: Ecto.Adapters.SQL.raise_sql_call_error/1
    (elixir 1.18.3) lib/enum.ex:1714: Enum."-map/2-lists^map/1-1-"/2
    (ecto_sql 3.13.2) lib/ecto/adapters/sql.ex:1219: Ecto.Adapters.SQL.execute_ddl/4
    (ecto_sql 3.13.2) lib/ecto/migration/runner.ex:348: Ecto.Migration.Runner.log_and_execute_ddl/3
    (elixir 1.18.3) lib/enum.ex:1714: Enum."-map/2-lists^map/1-1-"/2
    (elixir 1.18.3) lib/enum.ex:1714: Enum."-map/2-lists^map/1-1-"/2
    (ecto_sql 3.13.2) lib/ecto/migration/runner.ex:311: Ecto.Migration.Runner.perform_operation/3
    (stdlib 6.2.2) timer.erl:595: :timer.tc/2

Reproduction

https://github.com/serpent213/ash_postgres_multitenancy_migration_demo/

Expected Behavior

Working migration

[zachdaniel]

Please include in the issue an explanation of the changes that lead to invalid migrations.

[serpent213]

It's mentioned in the README:

Latest schema change:

user.ex:67: global? true

Removing the whole multitenancy block has the same effect, IIRC.

[zachdaniel]

Gotcha, thanks 😄 I won't be able to look into this in the near future, but PRs welcome!