incremental

Bugfixes

• Incremental could mis-identify that a project had opted in to version management.

  If a pyproject.toml in the current directory contained a [project] table with a name key, but did not contain the opt-in [tool.incremental] table, Incremental would still treat the file as if the opt-in were present and attempt to validate the configuration. This could happen in contexts outside of packaging, such as when creating a virtualenv. When operating as a setuptools plugin Incremental now always ignores invalid configuration, such as configuration that doesn't match the content of the working directory. (#106)

Bugfixes

• Incremental 24.7.0 would produce an error when parsing the pyproject.toml of a project that lacked the use_incremental=True or [tool.incremental] opt-in markers if that file lacked a [project] section containing the package name. This could cause a project that only uses pyproject.toml to configure tools to fail to build if Incremental is installed. Incremental now ignores such projects. (#100)

Misc

• #101

Features

• Incremental can now be configured using pyproject.toml. (#90)

• Incremental now provides a read-only Hatchling version source plugin. (#93)

Bugfixes

• Incremental no longer inserts a dot before the rc version component (i.e., 1.2.3rc1 instead of 1.2.3.rc1), resulting in version numbers in the canonical format. (#81)

• Incremental's tests are now included in the sdist release artifact. (#80)

Deprecations and Removals

• incremental[scripts] no longer depends on Twisted. (#88)

• Support for Python 2.7 has been dropped for lack of test infrastructure. We no longer provide universal wheels. (#86)

• Support for Python 3.5, 3.6, and 3.7 has been dropped for lack of test infrastructure. (#92)