DanCardin

What does your `alembic_engine` fixture look like? From the traceback, it seems like `connectable is an async generator, which seems like it'd indicate your `alembic_engine` isn't resolving into a real...

you should be able to use `async_=True`, we have a test for that: https://github.com/schireson/pytest-alembic/blob/main/examples/test_async_sqlalchemy_native/conftest.py I wouldn't expect you to need to set the `sqlalchemy.url` config_option, as `alembic_engine` should be being...

the `if connectable is None:` branch of your `env.py` should be being skipped because pytest-alembic ought to be setting the `connectable` for you, by subbing in the result of `alembic_engine`....

that's interesting, I had attempted to create a standalone package using pytest-alembic and pytest-mock-resources, while making similar in-place modifications `create_postgres_fixture` but i was still seeing the originally reported issue. Like...

there's a new version of pytest-mock-resources released (2.5.0) which addresses this issue, as far as the issue applies to it. If you're using the `--test-alembic` flag, i seem to still...

Okay, turns out there was an additional incompatibility with pytest-mock-resources versions >=2.4 which would fail with pytest-asyncio versions above 0.19, specifically with async under certain circumstances. So 2.5.1 should close...

Perhaps I'm not understanding your migration history. I attempted to recreate it from the above descriptions here: https://github.com/schireson/pytest-alembic/tree/dc/55/branched-history-downgrade, but `migrate_down_one` from `7f5b06f81aef` doesn't fail; so i assume i've gotten something...

I recreated your shortened history in a test example, and wasn't able to recreate the `Destination 79ee02b5e895 is not a valid downgrade target from current head(s)` message for whatever reason....

I altered the implementation of determining the history which helped in a different branched history scenario. I think I'd need a specific repro example for your history. When I was...

let us know if you can come up with a smaller reproducible example after 0.8.3. Otherwise i'm going to assume this is resolved due to lack of response/ability to reproduce.