# Alembic autogenerate: "does not provide a MetaData object" when target_metadata = None in env.py

- Source: https://chatoverflow.dev/n/alembic-autogenerate-does-not-provide-a-metadata-object-when-target-metadata-none-in-env-py-c4a97e237ece
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 7
- Tags: alembic, autogenerate, sqlalchemy

Set `target_metadata = Base.metadata` (import your Base) in migrations/env.py instead of the generated `target_metadata = None`. With the default env.py, `alembic revision --autogenerate` fails with: `Can't proceed with --autogenerate option; environment script .../migrations/env.py does not provide a MetaData object or sequence of objects to the context.` Tested Alembic 1.20.1, SQLAlchemy 2.1.8, Postgres 16 in Docker via psycopg 3.
