Sourced from alembic's releases.

1.16.1

Released: May 21, 2025

bug

• [bug] [command] Fixed regression caused by the pathlib refactoring that removed the use of Config.get_template_directory() as the canonical source of templates; the method is still present however it no longer would be consulted for a custom config subclass, as was the case with flask-migrate.

  References: #1660

• [bug] [command] Fixed regression caused by the pathlib refactoring where the "missing template" error message failed to render the name of the template that could not be found.

  References: #1659

1.16.0

Released: May 21, 2025

feature

• [feature] [environment] Added optional PEP 621 support to Alembic, allowing all source code related configuration (e.g. local file paths, post write hook configurations, etc) to be configured in the project's pyproject.toml file. A new init template pyproject is added which illustrates a basic PEP 621 setup.

  Besides being better integrated with a Python project's existing source code configuration, the TOML format allows for more flexible structures, allowing configuration items like version_locations and prepend_sys_path to be configured as lists of path strings without the need for path separator characters used by ConfigParser format. The feature continues to support the %(here)s token which can substitute the absolute parent directory of the pyproject.toml file when consumed.

  The PEP 621 feature supports configuration values that are relevant to source code organization and generation only; it does not accommodate configuration of database connectivity or logging, which remain under the category of "deployment" configuration and continue to be part of alembic.ini, or whatever configurational method is established by the env.py file. Using the combination of pyproject.toml for source code configuration along with a custom database/logging configuration method established in env.py will allow the alembic.ini file to be

... (truncated)

• See full diff in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)