Migrating to Alembic rel_1_18_4
Version rel_1_18_4 introduces 1 breaking change. This guide details how to update your code.
Released: 2/10/2026
1
Breaking Changes
1
Migration Steps
5
Affected Symbols
⚠️ Check Your Code
If you use any of these symbols, you need to read this guide:
Operations.add_columnOperations.add_column.inline_primary_keyOperations.add_column.inline_referencesColumnIntegerBreaking Changes
●Issue #1
The automatic rendering of the "PRIMARY KEY" keyword inline when adding a Column with `primary_key=True` via `Operations.add_column()` has been reverted. Previously added in 1.18.2, this behavior is now opt-in.
Migration Steps
- 1To restore the behavior of rendering PRIMARY KEY inline when using `Operations.add_column()` with a `Column(..., primary_key=True)`, set the new parameter `inline_primary_key=True` on the operation call.
Release Summary
This patch reverts the automatic inline rendering of PRIMARY KEY constraints in `Operations.add_column()` introduced in 1.18.2, making this behavior explicitly opt-in via the new `inline_primary_key` parameter.
Need More Details?
View the full release notes and all changes for Alembic rel_1_18_4.
View Full Changelog