Poetry-dynamic-versioning

Latest version: v1.2.0

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

Scan your dependencies

Page 1 of 9

1.2.0

* Added:
* `initial-content-jinja` option in `tool.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](https://github.com/mtkennerly/poetry-dynamic-versioning/pull/157))

1.1.1

* 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` and `enable` fields had already been changed.
Now, substitutions are reverted first before reverting `version` and `enable`.

1.1.0

* 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.

1.0.1

* Fixed:
* Compatibility with poetry-core 1.7.0, which removed the `poetry.core.semver` module.
* The `enable` command now constrains the plugin version to `>=1.0.0,<2.0.0`
to protect against any potential API changes.

1.0.0

* Fixed:
* Running `poetry dynamic-versioning` followed by `poetry build`
would leave the plugin enabled in the sdist's pyproject.toml.

1.0.0b3

* Fixed:
* The plugin can now update versions for dependencies that also use the plugin.

Page 1 of 9

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.