Poetry-dynamic-versioning

Latest version: v1.3.0

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

Scan your dependencies

Page 6 of 9

0.12.7

* Fixed:
* Parsing files containing special UTF-8 characters would result in an error.
Files are now assumed to be UTF-8.
([Contributed by rhorenov](https://github.com/mtkennerly/poetry-dynamic-versioning/pull/50))

0.12.6

* Fixed:
* The previous `bump` fix only applied to `format-jinja`. It has now been
fixed for other scenarios as well.

0.12.5

* Fixed:
* When the `bump` option was enabled, the version would be bumped even when on
a commit with a version tag. Now, no bumping occurs when on such a commit.

0.12.4

* Fixed:
* An incompatibility with `tox-poetry-installer` where the working directory
was received as a `str` instead of a `Path`.
([Contributed by cburgess](https://github.com/mtkennerly/poetry-dynamic-versioning/pull/41))

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.

Page 6 of 9

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.