Skip to content

Releases: jwodder/versioningit

v3.1.1 — Fix a test

29 Apr 11:19
v3.1.1
Compare
Choose a tag to compare
  • Correctly mark a certain test as requiring Mercurial

v3.1.0 — Improve some error messages

16 Mar 19:49
v3.1.0
Compare
Choose a tag to compare
  • When git describe fails to retrieve a tag, the resulting log/error message now includes all options passed to the command (based on contribution by @jenshnielsen)
  • When hg log fails to retrieve a tag, the resulting log/error message now includes the tag pattern passed to latesttag(), if any

v3.0.0 — Support `onbuild` with Hatch

14 Dec 00:15
v3.0.0
Compare
Choose a tag to compare
  • Migrated from setuptools to hatch
  • Support using the onbuild step with Hatch
  • Breaking: The build_dir argument passed to Versioningit.do_onbuild() and onbuild method callables has been changed to an OnbuildFileProvider ABC

v2.3.0 — Hatch support

19 Nov 14:02
v2.3.0
Compare
Choose a tag to compare
  • Always read .hg_archival.txt files using UTF-8 encoding
  • Added support for using versioningit with Hatch

v2.2.1 — Improve an error and tests

22 Sep 20:31
v2.2.1
Compare
Choose a tag to compare
  • Raise a ConfigError if the selected tool.versioningit.format field is not a string
  • Update tests for pydantic 2.0
  • Update tests for Python 3.12
  • Support Python 3.12

v2.2.0 — Importable command classes

11 Feb 23:04
v2.2.0
Compare
Choose a tag to compare
  • The custom setuptools command classes can now be imported directly from the versioningit.cmdclass module as an alternative to calling get_cmdclasses()

v2.1.0 — Python updates

25 Oct 22:45
v2.1.0
Compare
Choose a tag to compare
  • Drop support for Python 3.6
  • Support Python 3.11
  • Use tomllib on Python 3.11

v1.1.2 — Backport 2.0.1 fix

12 Aug 20:50
v1.1.2
Compare
Choose a tag to compare
  • Backport "Don't run the onbuild step under setuptools' upcoming PEP 660 editable mode" from v2.0.1 (contributed by @abravalheri)

v2.0.1 — Don't run `onbuild` in PEP 660 editable mode

01 Aug 16:11
v2.0.1
Compare
Choose a tag to compare
  • Don't run the onbuild step under setuptools' upcoming PEP 660 editable mode (contributed by @abravalheri)

v2.0.0 — `{version_tuple}` write + onbuild placeholder, et alii

12 Jun 22:23
v2.0.0
Compare
Choose a tag to compare
  • The {version} placeholder in the "basic" format step has been renamed to {base_version}. The old name remains usable, but is deprecated.
    • Breaking: The version argument passed to Versioningit.do_format() and format method callables has been renamed to base_version.
  • A {version_tuple} field, along with the fields available in the format step, is now available for use in templates in the write and onbuild steps.
    • New step and subtable: "template-fields"
    • Breaking: The version arguments passed to Versioningit.do_write(), Versioningit.do_onbuild(), run_onbuild(), and write & onbuild method callables have been replaced with template_fields arguments
    • Added a get_template_fields_from_distribution() function for use by callers of run_onbuild()
  • Versioningit.get_version() now takes optional write and fallback arguments
  • The onbuild step is no longer run when building from an sdist; the configuration therefore no longer needs to be idempotent
  • Drop setuptools runtime dependency
    • setuptools is only needed for get_cmdclasses(), which should only be called in an environment where setuptools is already installed.
  • Prevent log messages from being printed twice under recent versions of setuptools
  • Values supplied for the require-match parameters of the tag2version and onbuild steps must now actually be booleans; previously, values of any type were accepted and were converted to booleans.
  • Added a Versioningit.run() method that returns a structure containing all intermediate & final values
  • "git" method: {author_date} and {committer_date} are no longer "clamped" to less than or equal to {build_date}. This undocumented behavior was based on a misinterpretation of the SOURCE_DATE_EPOCH spec, and was even applied when SOURCE_DATE_EPOCH was not set.
  • When resolving entry points, if multiple entry points with the given group & name are found, error instead of using the first one returned