Poetry-dynamic-versioning

Latest version: v1.7.1

Safety actively analyzes 715081 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 8 of 11

0.12.3

* Fixed:
* Previously, when building a source distribution with `poetry build`, the
plugin's config section would retain the `enable = true` setting, which
would then cause an error when installing the artifact since the VCS info
would not be available.
(This was not an issue for wheels generated by `poetry build`.)

The dynamic version from build time is still present in the source
distribution, so there is no need for the plugin at install time.
Therefore, the plugin now temporarily sets `enable = false` so that that
value will be placed in the source distribution, then restores the original
setting for development purposes.

0.12.2

* Fixed:
* Another possible exception when applying patches if only `poetry-core` was
installed and not the Poetry tool, particularly combined with Tox.

0.12.1

* Fixed:
* Possible exception when applying patches if only `poetry-core` was
installed and not the Poetry tool.

0.12.0

* Added:
* `tagged-metadata` option, for the corresponding Dunamai feature.
([Contributed by mariusvniekerk](https://github.com/mtkennerly/poetry-dynamic-versioning/pull/32))

0.11.0

* Added:
* `bump` option.
* Fixed:
* `poetry shell` did not clean up after itself.

0.10.0

* Added:
* Support for patching `poetry-core` when used as a standalone build system.

Page 8 of 11

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.