Originally created by @Blacks-Army on GitHub (Jul 1, 2025).
When upgrading Pangolin to version 1.6 using a PostgreSQL database, the container attempts to run migrations against a SQLite database. Since the SQLite database does not exist, the migration fails and the container does not start.
The startup process should check the database type before attempting any migrations, or respect the existing database configuration.
I can provide more details (logs, configuration, etc.) by tomorrow if needed.
Originally created by @Blacks-Army on GitHub (Jul 1, 2025).
When upgrading Pangolin to version 1.6 using a PostgreSQL database, the container attempts to run migrations against a SQLite database. Since the SQLite database does not exist, the migration fails and the container does not start.
The startup process should check the database type before attempting any migrations, or respect the existing database configuration.
I can provide more details (logs, configuration, etc.) by tomorrow if needed.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @Blacks-Army on GitHub (Jul 1, 2025).
When upgrading Pangolin to version 1.6 using a PostgreSQL database, the container attempts to run migrations against a SQLite database. Since the SQLite database does not exist, the migration fails and the container does not start.
The startup process should check the database type before attempting any migrations, or respect the existing database configuration.
I can provide more details (logs, configuration, etc.) by tomorrow if needed.
@miloschwartz commented on GitHub (Jul 2, 2025):
Ah yeah- typo in the migrations file. Just release a 1.6.2 patch which I think should fix this. Lmk!
@Blacks-Army commented on GitHub (Jul 2, 2025):
It works now thanks