Skip to content

v2.1.0

Choose a tag to compare

@axelander axelander released this 18 Aug 08:37
· 2 commits to release/v2.1 since this release

Important note

Before upgrading to Eneo 2.1, review the database migration guidance below.
Manual action is required only for deployments previously upgraded from
v2.0.1 to v2.1.0-rc.1. All other supported upgrade paths require no
additional steps.

Database migration fix

Eneo 2.1 fixes an Alembic migration ordering issue introduced in
v2.1.0-rc.1. On deployments that upgraded from v2.0.1 to v2.1.0-rc.1, nine
database migrations (SCIM, model cost, model lifecycle, and transcription
changes) were silently skipped while the database was still marked as fully
migrated.

Direct upgrades from v2.0.0 or v2.0.1 to the final v2.1 release are safe.
Fresh installations require no manual action.

If you previously upgraded from v2.0.1 to v2.1.0-rc.1, repair the migration
state after deploying v2.1, with the application stopped.

First, point Alembic back at the last correctly applied revision:

UPDATE alembic_version
SET version_num = '202605061100';

Then apply the skipped migrations and mark the database as current:

uv run alembic upgrade 20260603_transcription_migrate
uv run alembic stamp head

Do not run alembic upgrade head instead of the two commands above. Several
migrations after the repaired revision were already applied during the
rc.1 upgrade and are not safe to re-run: a plain upgrade to head fails with
duplicate object errors and leaves the migration state partially advanced.
The commands above apply exactly the nine skipped migrations and then record
the correct final state without re-running anything else.

What's Changed

New Contributors

Full Changelog: v1.5.2...v2.1.0