1.11.1

Released: May 17, 2023

bug

• [bug] [autogenerate] [regression] As Alembic 1.11.0 is considered a major release (Alembic does not use semver, nor does its parent project SQLAlchemy; this has been clarified <versioning_scheme> in the documentation), change #1130 modified calling signatures for most operations to consider all optional keyword parameters to be keyword-only arguments, to match what was always documented and generated by autogenerate. However, two of these changes were identified as possibly problematic without a more formal deprecation warning being emitted which were the table_name parameter to Operations.drop_index(), which was generated positionally by autogenerate prior to version 0.6.3 released in 2014, and type_ in Operations.drop_constraint() and BatchOperations.drop_constraint(), which was documented positionally in one example in the batch documentation.

  These two signatures have been restored to allow those particular parameters to be passed positionally. A future change will include formal deprecation paths (with warnings) for these arguments where they will again become keyword-only in a future "Significant Minor" release.

  References: #1243, #1245

• [bug] [typing] Fixed typing use of ~sqlalchemy.schema.Column and other generic SQLAlchemy classes.

  References: #1246

• [bug] [regression] [typing] Restored the output type of Config.get_section() to include Dict[str, str] as a potential return type, which had been changed to immutable Mapping[str, str]. When a section is returned and the default is not used, a mutable dictionary is returned.

  References: #1244