Releases: mtkennerly/poetry-dynamic-versioning
Releases · mtkennerly/poetry-dynamic-versioning
v1.6.0 (2025-01-10)
- Added:
- CLI:
show
command to print the version without changing any files.
- CLI:
v1.5.2 (2025-01-09)
- Fixed:
- The formatting of
project.dynamic
andtool.poetry.version
could be changed when triggering the plugin viapoetry dynamic-versioning
orpip install
(but not viapoetry build
orpoetry-dynamic-versioning
).
- The formatting of
v1.5.1 (2025-01-09)
- Fixed:
- Array formatting was not preserved when changing
project.dynamic
in pyproject.toml. (Contributed by edgarrmondragon)
- Array formatting was not preserved when changing
v1.5.0 (2025-01-05)
- Added:
- CLI: When pyproject.toml contains the
project
section, theenable
command will add the required fields for Poetry 2.0.0+.
- CLI: When pyproject.toml contains the
- Fixed:
- For compatibility with Poetry 2.0.0, adjusted Poetry constraint from
^1.2.0
to>=1.2.0
. - For compatibility with Poetry 2.0.0, when inserting the dynamic version into pyproject.toml with PEP 621 mode activated, the plugin ensures not to set
project.version
andtool.poetry.version
at the same time. - An
UnboundLocalError
could happen when pyproject.toml was misconfigured.
- For compatibility with Poetry 2.0.0, adjusted Poetry constraint from
v1.4.1 (2024-09-10)
- Fixed:
- The
enable
command would fail when the pyproject.toml tables were out of order.
- The
v1.4.0 (2024-06-17)
- Added:
-
The plugin now supports Poetry's upcoming PEP-621 functionality. More info here: python-poetry/poetry#3332
If your pyproject.toml defines
tool.poetry.name
, then the plugin will preserve its existing behavior.However, if your pyproject.toml:
- does not define
tool.poetry.name
- defines
project.name
- defines
project.dynamic
to include"version"
- does not define
project.version
...then the plugin will enable its PEP-621 functionality.
Because PEP-621 support is not yet released and finalized in Poetry itself, it is also subject to change in the plugin.
- does not define
-
v1.3.0 (2024-04-29)
- Added:
pattern-prefix
option to add a prefix to the version tag pattern.ignore-untracked
option to control the detection of dirty state.from-file
config section to read a version from a file instead of the VCS.POETRY_DYNAMIC_VERSIONING_DEBUG
environment variable for some logging.
- Changed:
- Updated Dunamai to 1.21.0+ for the latest features.
v1.2.0 (2023-12-02)
- Added:
initial-content-jinja
option intool.poetry-dynamic-versioning.files
section.
- Fixed:
- Line ending style was not preserved in some cases because of the default behavior of
pathlib.Path.read_text
. To avoid this,pathlib.Path.read_bytes
is used instead now. (Contributed by nardi)
- Line ending style was not preserved in some cases because of the default behavior of
v1.1.1 (2023-10-27)
- Fixed:
- Custom substitutions in pyproject.toml weren't cleaned up correctly. This was because the plugin would record the "original" content of the file after the
version
andenable
fields had already been changed. Now, substitutions are reverted first before revertingversion
andenable
.
- Custom substitutions in pyproject.toml weren't cleaned up correctly. This was because the plugin would record the "original" content of the file after the
v1.1.0 (2023-10-01)
- Added:
tool.poetry-dynamic-versioning.files
config section. This allows you to create a file in a default state before applying substitutions to it. You can also leave the substitutions in place when the plugin deactivates.